Bug 1123807

Summary: [RFE][test run] The btn for changing caserun's status in caserun's summary is more convenient than in caserun's detail.
Product: [Other] TCMS Reporter: yangqiu <qiyang>
Component: ApplicationAssignee: Yang Ren <ryang>
Status: NEW --- QA Contact: Nobody <nobody>
Severity: low Docs Contact:
Priority: low    
Version: 3.8.9CC: cqi, junzhang, ryang, vchen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
[RFE][test run] The btn for changing caserun's status in caserun's summary is more convenient than in caserun's detail. none

Description yangqiu 2014-07-28 10:00:36 UTC 
Created attachment 921746 [details]
[RFE][test run] The btn for changing caserun's status in caserun's summary is more convenient than in caserun's detail.

Description of problem:
After execute the case many times, qa knew what's the test steps from the case summary, so qa need not to expand caserun's detail to get the test steps, but qa have to expand caserun's detail to mark test result. Although 'status' menu offer the function, for most of qa, they does not know the function.  

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Enter a test run detail page.
https://tcms-stage-01.app.eng.bne.redhat.com/run/154530/
2.
3.

Actual results:
The btn for changing caserun's status is in the caserun's detail.

Expected results:
The btn for changing caserun's status move to caserun's summary.

Additional info: