Closed
Bug 256336
Opened 21 years ago
Closed 20 years ago
Milestones are not ordered by sort order in report graph
Categories
(Bugzilla :: Reporting/Charting, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 142394
People
(Reporter: jeremy, Assigned: gerv)
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040614 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7) Gecko/20040614 Firefox/0.8
I was generated a report, and selected "Severity" as my vertical axis, and
"Target Milestone" as my horizontal axis, I expected to see a graph (in time
basically), or bug severity. However, the Target milestones were sorted alpha,
instead of by the sort key, which is used to show some sort of order in time
(right?).
Reproducible: Always
Steps to Reproduce:
1. Have milestones where the sort key is different that the alpha list
2. Create a report with severity (anything) vs Target Milestone
3. ??
4. Profit... (oops, sorry)
Actual Results:
The graph came out, but by horz axis was not what I expected
Expected Results:
The Target milestons should have been ordered by sort key.
| Reporter | ||
Comment 1•21 years ago
|
||
Sorry, forgot the submit Bugzilla version (2.18rc2)
Version: unspecified → 2.18
| Assignee | ||
Comment 2•21 years ago
|
||
True, but hard to fix :-| I hope to look into it at some point. Sorting in
charts is currently a nightmare.
Gerv
Updated•20 years ago
|
QA Contact: mattyt-bugzilla → default-qa
Comment 3•20 years ago
|
||
Even so, this bug seems valid. Either mark as a duplicate of bug 142394 or
confirm and reassign to nobody (bug 142394 comment 8).
Comment 4•20 years ago
|
||
*** This bug has been marked as a duplicate of 142394 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Unfortunately it looks like the bug I reported is likely a duplicate of this issue as well (bug#407762).
It really seems like resolving this bug as duplicate of bug#142394 is a cop-out since bug#142394 really proposes an enhancement to allow user sortable reports whereas in this bug and in the one I reported we are mainly looking for a defect in the existing functionality to be fixed.
You need to log in
before you can comment on or make changes to this bug.
Description
•