Hide Forgot
Description of problem: After select no/one/more/all plan(s) and click "export" botton, Their result are totally same Version-Release number of selected component (if applicable): 3.4.5 on stage How reproducible: Steps to Reproduce: 1.In search list select no / one / more / all plan(s) 2.Click "export" button. 3.choose save/open the file and click "OK" Actual results: select no/one/more/all plan(s) and click "export" botton, the contents of xml file of result are totally same. Expected results: contents should different. Additional info:
Created attachment 499747 [details] Screenshot Update the actual result: export one/more/all plan will warning that"At least one plan/case is required."
Additional info: In search cases list have the same problem: Can not export one/more/all case(s) in search cases list
Verify version: 3.4-7 -->FAIL Actual result: No matter select one / more / all plan(s) to export plan/case/run will export all.
(In reply to comment #3) > Verify version: 3.4-7 -->FAIL > > Actual result: No matter select one / more / all plan(s) to export > plan/case/run will export all. update the verification result: Verify version: 3.4-7 -->PASS Actual result: can export the selected plan/case
verify version 3.3-8 on stage Verify steps: 1.Search some plans/cases/runs in advanced search. 2.Select no plan/case/run. 3.Click "Printable copy"/"Export", then come out warning "At least one plan is required. Return to homepage". 4.Click "Return to homepage" Verify result: FAILED. After Click "Return to homepage", Come out warning "Bad Request". Please refer to bug #706839
Sorry my fault! verify version 3.4-8 on stage (In reply to comment #5) > verify version 3.3-8 on stage > > Verify steps: > 1.Search some plans/cases/runs in advanced search. > 2.Select no plan/case/run. > 3.Click "Printable copy"/"Export", then come out warning "At least one plan is > required. Return to homepage". > 4.Click "Return to homepage" > > Verify result: FAILED. > After Click "Return to homepage", Come out warning "Bad Request". > > Please refer to bug #706839