Edgewall Software

Ticket #2209 (closed enhancement: fixed)

Opened 3 years ago

Last modified 4 weeks ago

Sort milestones by completed date and due date

Reported by: anonymous Owned by: rblank
Priority: normal Milestone: 0.11.2
Component: roadmap Version: 0.9b2
Severity: minor Keywords: patch
Cc: remy.blank@…

Description

Currently, the milestones are sorted by due date on the roadmap and in custom queries when grouped by milestone. If some of the milestones have a due date and others do not, the sort is not as desired for completed milestones. The completed date should be used for the sort rather then the due date for completed milestones.

A workaround at the moment is to enter a due date the same as the completed date for those milestones without a due date. It is inconvenient to remember to do that, but workable.

Attachments

2209-query-sort-milestone-r7439.patch (2.7 KB) - added by Remy Blank <remy.blank@…> 4 months ago.
Patch against 0.11-stable fixing sorting by milestone in queries
2209-query-sort-milestone-r7443.patch (4.0 KB) - added by Remy Blank <remy.blank@…> 4 months ago.
Same patch, additionally fixed test cases

Change History

  Changed 3 years ago by cmlenz

  • status changed from new to assigned
  • milestone set to 0.9.1

  Changed 3 years ago by cmlenz

  • milestone changed from 0.9.1 to 0.9.2

  Changed 3 years ago by cmlenz

  • milestone changed from 0.9.3 to 0.9.4

follow-up: ↓ 15   Changed 3 years ago by cboos

See r2758 for a description of the new Milestone sort order implemented for the roadmap.

What's left to be done is something similar for the query module, when the tickets are grouped by Milestones.

  Changed 3 years ago by cmlenz

  • milestone changed from 0.9.4 to 0.10

  Changed 2 years ago by anonymous

please ignore, testing anonymous comments...

  Changed 2 years ago by anonymous

Testing

  Changed 2 years ago by anonymous

Would you like some tasty viagra?

  Changed 2 years ago by anonymous

http://www.bugviagra.com BUY BUY BUY!!!

  Changed 2 years ago by cboos

This is not a test site. Please stop this.

  Changed 2 years ago by cboos

Oops, just saw your mail on Trac Dev ;) Well simulated, jonas ;)

  Changed 2 years ago by cmlenz

  • status changed from assigned to new
  • milestone changed from 0.10 to 0.11

Ah well, postponing again.

  Changed 6 months ago by anonymous

  • priority changed from low to normal

  Changed 5 months ago by techtonik <techtonik@…>

Query/filter functionality is a good idea. For possible uses see also bug #7342

Changed 4 months ago by Remy Blank <remy.blank@…>

Patch against 0.11-stable fixing sorting by milestone in queries

in reply to: ↑ 4   Changed 4 months ago by Remy Blank <remy.blank@…>

  • cc remy.blank@… added
  • keywords patch added

Replying to cboos:

What's left to be done is something similar for the query module, when the tickets are grouped by Milestones.

The patch above fixes sorting of query results by milestone, by applying the same sort order as used in the roadmap. The only exception is that it doesn't use the natural sort order when comparing the milestone names (if both completed and due are equal). If anybody knows how to perform a natural sort in SQL, please let me know.

The patch also refactors the query sort code to simplify the SQL construction and removing unnecessary duplication.

Changed 4 months ago by Remy Blank <remy.blank@…>

Same patch, additionally fixed test cases

  Changed 4 months ago by Remy Blank <remy.blank@…>

I had forgotten to run the test suite. The second patch also fixes the test cases.

  Changed 3 months ago by rblank

  • status changed from new to closed
  • resolution set to fixed
  • milestone changed from 0.11.3 to 0.11.2

Patch applied in [7483].

  Changed 4 weeks ago by cboos

  • owner changed from cmlenz to rblank

Add/Change #2209 (Sort milestones by completed date and due date)

Author



Change Properties
<Author field>
Action
as closed
Next status will be 'reopened'
to The owner will change from rblank. Next status will be 'closed'
 
Note: See TracTickets for help on using tickets.