Bug 1085322 - [test plan][cases]When search case at cases tab in test plan page, the 'Autoproposed' option is ineffective.
Summary: [test plan][cases]When search case at cases tab in test plan page, the 'Autop...
Keywords:
Status: NEW
Alias: None
Product: TCMS
Classification: Other
Component: Application
Version: 3.8.5
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 3.9.1
Assignee: cqi
QA Contact: Nobody
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-08 11:29 UTC by yangqiu
Modified: 2023-10-20 16:24 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)
When search caes at cases tab in test plan page, the 'Autoproposed' option is ineffective (194.48 KB, image/jpeg)
2014-04-08 11:29 UTC, yangqiu
no flags Details

Description yangqiu 2014-04-08 11:29:39 UTC
Created attachment 883981 [details]
When search caes at cases tab in test plan page, the 'Autoproposed' option is ineffective

Description of problem:
as subject

Version-Release number of selected component (if applicable):
v3.8.7-1 on qa server

How reproducible:
100%

Steps to Reproduce:
1.There is a plan includes a case of which the Automated value is Manual(Autoproposed)
2.Enter the plan detail page, then enter cases tab page.
https://tcms.app.qa.eng.nay.redhat.com/plan/10680/yang-qiu-ce-shi-plan-bbb#testcases
3.Click Show filter options to expand case filter option.
4.Choose Automated is Manual and selected Autoproposed, click 'filter cases' btn, check the result.
5.Choose Automated is Manual and unselected Autoproposed, click 'filter cases' btn, check the result.

Actual results:
For step 4: system filter the case.
For step 5: system filter the case.

Expected results:
For step 4: system filter the case.
For step 5: system can not filter the case.


Additional info:

Comment 1 yangqiu 2014-05-15 06:39:18 UTC
The above issue also happened in Search Cases page(Click 'testing-search cases' link to enter).


Note You need to log in before you can comment on or make changes to this bug.