Bug 1125828

Summary: [Testing report] Generate testing report By Case Priority, the Priority order for different builds were different.
Product: [Other] TCMS Reporter: yangqiu <qiyang>
Component: UsabilityAssignee: cqi
Status: VERIFIED --- QA Contact: Nobody <nobody>
Severity: low Docs Contact:
Priority: low    
Version: 3.8.10CC: cqi, jcai, junzhang, ryang, xkuang, yuwang
Target Milestone: ---   
Target Release: 3.8.10   
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
[Testing report] Generate testing report By Case Priority, the Priority order for different builds were different. none

Description yangqiu 2014-08-01 07:43:02 UTC 
Created attachment 923122 [details]
[Testing report] Generate testing report By Case Priority, the Priority order for different builds were different.

Description of problem:
as summary.

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

How reproducible:
100%

Steps to Reproduce:
1.Enter testing report page, choose product as 'qiyang test product', generate report by Case Priority.
https://tcms-devel.app.eng.nay.redhat.com/report/testing/?r_product=343&r_created_since=&r_created_before=&report_type=per_priority_report
2.Inspect the order for Priority between the two build.

Actual results:
the order for Priority between the two build were different.

Expected results:
the order for Priority between the two build were same: P1,P2,P3,P4,P5

Additional info:
Comment 1 cqi 2014-08-04 02:31:52 UTC 
fixed. in the priority column, priorities are ordered by name, for example,

----------------+----+----+----
 MR-16 Sprint 2 | P1 | 10 | 20
                | P3 | 10 | 20
                | P5 | 10 | 20
-------------------------------
Comment 2 yangqiu 2014-08-06 07:06:13 UTC 
verify this issue on 3.8.10-1 on devel server.--->Pass
verify steps are same as description.