MantisBT - TestLink
View Issue Details
0004231TestLinkTest Plan (builds, milestones, test assign)public2011-02-08 15:042013-05-30 19:42
atrabelsi 
asimon 
urgentfeature requestalways
closedfixed 
1.9.1 (bug fixing) 
1.9.5 (2012 Q4 - bug fixing) 
Testlink
READY FOR TESTING
0004231: Add a filter on test importance while adding TCs to a test plan
Add a filter on test importance while adding TCs to a test plan
This issue is very important since the test plan is principally based on test importance.
No tags attached.
duplicate of 0004217new asimon No way to filter by "Test importance" 
has duplicate 0004413closed Julian Test Priority Filter not availble while Adding Test Cases to Test Plan 
has duplicate 0004071closed Julian Test Plan definition improvment 
related to 0002985closed Julian Expose test case IMPORTANCE (NOT priority) as a column in the 'Add / Remove Test cases to Test Plan' frame. 
png Test Importance Filter not provided while adding test cases to Test Plan.PNG (68,237) 2011-04-14 09:27
http://mantis.testlink.org/file_download.php?file_id=2296&type=bug
png
Issue History
2011-02-08 15:04atrabelsiNew Issue
2011-02-08 16:13JulianAssigned To => asimon
2011-02-08 16:13JulianStatusnew => assigned
2011-04-14 09:09JulianRelationship addedhas duplicate 0004413
2011-04-14 09:27spacompFile Added: Test Importance Filter not provided while adding test cases to Test Plan.PNG
2011-04-14 09:36JulianRelationship addedrelated to 0004217
2011-04-14 11:18spacompNote Added: 0014615
2011-04-14 11:21JulianRelationship addedrelated to 0002985
2011-04-15 11:53JulianNote Added: 0014651
2011-04-15 16:36JulianRelationship addedhas duplicate 0004071
2011-04-15 16:50atrabelsiNote Added: 0014661
2011-04-17 07:24JulianNote Added: 0014684
2011-06-03 07:36atrabelsiNote Added: 0015106
2011-06-03 08:00JulianNote Added: 0015107
2012-08-30 10:15asimonRelationship replacedparent of 0004217
2012-10-10 12:03asimonRelationship replacedduplicate of 0004217
2012-10-10 12:04asimonTask Workflow Status => READY FOR TESTING
2012-10-10 12:04asimonStatusassigned => resolved
2012-10-10 12:04asimonFixed in Version => 1.9.5 (2012 Q4 - bug fixing)
2012-10-10 12:04asimonResolutionopen => fixed
2013-05-30 19:42fmanStatusresolved => closed

Notes
(0014615)
spacomp   
2011-04-14 11:18   
Also See Issue No 0002985
(0014651)
Julian   
2011-04-15 11:53   
Here we might not be able to fix, because:

Imagine a test case with 3 version:
v1 -> importance = low
v2 -> importance = medium
v3 -> importance = high

When we want to add this test case to test plan we do not know what the appropriate importance could be.
(0014661)
atrabelsi   
2011-04-15 16:50   
Genarally, Importance will be the same for the 3 versions.

Suppose that a test case has 3 versions:
v1 -> Execution type = Manual
v2 -> importance = Manual
v3 -> importance = Automated

I think that the filter has to applicable on the last version.
(0014684)
Julian   
2011-04-17 07:24   
please explain your last comment.

v1 -> Execution type = Manual
v2 -> importance = Manual
v3 -> importance = Automated

copy/paste error?
(0015106)
atrabelsi   
2011-06-03 07:36   
sorry!!!

the idea is that we can have a test case with 3 versions and each time a different Execution type.

v1 -> Execution type = Manual
v2 -> Execution type = Manual
v3 -> Execution type = Automated

The Execution type filter is already done (i think on last version). So you can add Importance also.
(0015107)
Julian   
2011-06-03 08:00   
This issue is targeted for 2.0 - we will find a solution