MantisBT - TestLink
View Issue Details
0004253TestLinkTest Plan (builds, milestones, test assign)public2011-02-17 15:062011-03-18 19:08
phidotnet 
asimon 
normalmajoralways
closedfixed 
Windows 7 + Chrome
1.9.1 (bug fixing) 
1.9.2 (2011 Q2 - bug fixing) 
MySQL
Chrome
0004253: Filter 'Result=Not Run' in page "Assign Test Case Execution" does not work if test plan has ONLY 1 build
In case the test plan has only one build, the filter does not work if user wants to list Not Run test cases.
1) Create new test plan
2) Add 5 test cases into the test plan
3) Create a new build in the test plan
4) Execute/Update test result for 3 test cases for the build
5) Navigate to page "Assign Test Case Execution"
6) Filter Not Run test cases to assign to someone else

Actual result:
There is NOT any test cases listed

Expected result:
There are 2 Not Run test cases showed in the left tree
(Attached screen shots are captured when the issue happens)

- If the test plan has more than 1 build the issue does not happen
- The fix fix_4203.zip has been applied on the tested build
No tags attached.
child of 0004185closed fman Availables Fixes for 1.9.1 (Prague) 
png Issue - Filter in Assign Test Case Execution.png (56,511) 2011-02-17 15:06
http://mantis.testlink.org/file_download.php?file_id=2174&type=bug
png

png Correct - General Test Plan Metrics.png (44,729) 2011-02-17 15:07
http://mantis.testlink.org/file_download.php?file_id=2175&type=bug
png

png Correct - Filter in Test Execution.png (70,536) 2011-02-17 15:09
http://mantis.testlink.org/file_download.php?file_id=2176&type=bug
png
Issue History
2011-02-17 15:06phidotnetNew Issue
2011-02-17 15:06phidotnetFile Added: Issue - Filter in Assign Test Case Execution.png
2011-02-17 15:07phidotnetFile Added: Correct - General Test Plan Metrics.png
2011-02-17 15:09phidotnetFile Added: Correct - Filter in Test Execution.png
2011-02-21 19:37fmanNote Added: 0013713
2011-02-22 08:27asimonNote Added: 0013720
2011-02-22 08:41asimonAssigned To => asimon
2011-02-22 08:41asimonStatusnew => assigned
2011-02-22 15:25asimonNote Added: 0013722
2011-02-22 15:26asimonRelationship addedchild of 0004185
2011-02-22 15:26asimonStatusassigned => resolved
2011-02-22 15:26asimonFixed in Version => 1.9.2 (2011 Q2 - bug fixing)
2011-02-22 15:26asimonResolutionopen => fixed
2011-03-18 19:08fmanNote Added: 0013957
2011-03-18 19:08fmanStatusresolved => closed

Notes
(0013713)
fman   
2011-02-21 19:37   
Reminder sent to: asimon

do you think you can take care of this ?
(0013720)
asimon   
2011-02-22 08:27   
I've just reproduced the bug - I'll take a look and check if I find the problem.
(0013722)
asimon   
2011-02-22 15:25   
Fix for 1.9: http://gitorious.org/testlink-ga/testlink-code/commit/8adabf17dfb1b8ee78b98fe0b9f5522f2e2170fa [^]

Fix for master: http://gitorious.org/testlink-ga/testlink-code/commit/6ec5cb9ce9b56b79955c9544a40221f998553ffc [^]

Found & fixed for both branches. The problem was that the value of the disabled select input (filter method) was not sent by the form, so the wrong filter method was chosen to filter the results in this special case.
(0013957)
fman   
2011-03-18 19:08   
release - 1.9.2 - 20110320