Bug 1038576 - [test plan]After change the cases status in reviewing tab, unable show in cases except refresh
Summary: [test plan]After change the cases status in reviewing tab, unable show in cas...
Keywords:
Status: VERIFIED
Alias: None
Product: TCMS
Classification: Other
Component: Application
Version: 3.8.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: cqi
QA Contact: Nobody
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-05 11:44 UTC by Jin Zhao
Modified: 2022-03-14 03:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Jin Zhao 2013-12-05 11:44:29 UTC
Description of problem:


Version-Release number of selected component (if applicable):
V3.8.5-3 on https://tcms.app.qa.eng.nay.redhat.com

How reproducible:
Always


Steps to Reproduce:
1.Browser test plan in reviewing tab, such as https://tcms.app.qa.eng.nay.redhat.com/plan/10641/copy-of-copy-of-test-plan-for-beacon-product-360#reviewcases
2.Select some cases, 
3.Click Status and Change to CONFIRMED, click ok button
3.Click cases tab

Actual results:
Unable to show the change cases which selected in step 2, except I refresh page

Expected results:
Can show the selected cases.

Additional info:

Comment 1 cqi 2013-12-11 04:39:43 UTC
Fixed.

Comment 2 yangqiu 2013-12-23 05:55:09 UTC
Verify the bug on devel server.--->Fass

Steps to verify:
1. Enter test plan page.
2. In case tab, change some cases status from confirmed to proposed|disabled|need_update.
3. Do not fresh the page, check the changed cases shown in reviewing cases tab or not.
4. In reviewing cases tab, change some cases status from proposed|disabled|need_update to confirmed.
5. Do not fresh the page, check the changed cases shown in cases tab or not.

Actual results:
For step 3: the changed cases shown in reviewing cases tab correctly.
For step 5: the changed cases shown in cases tab correctly.


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