Bug 1134166 - [test plan] when user remove tag at reviewing case tag in test plan detail page, system returns 500 error.
Summary: [test plan] when user remove tag at reviewing case tag in test plan detail pa...
Keywords:
Status: VERIFIED
Alias: None
Product: TCMS
Classification: Other
Component: Application
Version: 3.8.10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.8.10
Assignee: Yang Ren
QA Contact: Nobody
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-27 03:34 UTC by yangqiu
Modified: 2023-10-20 16:23 UTC (History)
5 users (show)

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


Attachments (Terms of Use)
[test plan] when user remove tag at reviewing case tag in test plan detail page, system returns 500 error. (154.70 KB, application/octet-stream)
2014-08-27 03:34 UTC, yangqiu
no flags Details

Description yangqiu 2014-08-27 03:34:44 UTC
Created attachment 931239 [details]
[test plan] when user remove tag at reviewing case tag in test plan detail page, system returns 500 error.

Description of problem:
as summary.

Version-Release number of selected component (if applicable):
v3.8.10-1 on stage

How reproducible:
100%

Steps to Reproduce:
1.Enter a plan detail page, then enter reviewing case tab.
https://tcms-stage-01.app.eng.bne.redhat.com/plan/14878/qiyang-test-plan-333#testcases
2.Select all test case, then click 'tag - remove tag' link to remove one of tag.

Actual results:
system returns 500 error.

Expected results:
system remove the selected tag.

Additional info:

Comment 1 jianchen 2014-08-27 08:15:40 UTC
This bug can't reproduce in stage server now.

Comment 2 Xu Lei 2014-08-28 02:03:08 UTC
I think there was an exception when remove tag and trigger except statement, and in this statement an undefine varaible was here. it will raise a error.

Comment 3 Tingting Zhao 2014-08-28 02:56:04 UTC
verify on qa server with 3.8.10-2 ------->pass
verify steps are the same as the description.


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