| Summary: | sort builds in predictable order | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Sam Davis <sam.davis> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | Keywords: | helpwanted |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Sam Davis
Builds can be sorted by clicking on the column headers, consecutive clicks set to ASCENDING, DESCENDING, NOTSORTED ad infinitum. So propose closing as WORKSFORME Is this a real bug or is the description too short? Upon further investigation, here's the behaviour I see with the different sorting options: * Ascending: build servers are sorted in *descending* order, builds in ascending order by status, builds with the same status are in random order * Descending: build servers are sorted in descending order, builds in descending order by status, builds with the same status are in random order * the mysterious third option: build servers are sorted in ascending order, builds in ascending order by name This is pretty confusing. It would be better to be able to explicitly control whether sorting is by status or by name, and to sort build servers separately from builds. Lowering priority as the current behaviour works well enough. Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn |