#972 Relative ticket prioritization

sf-8 (45)
Mark Ramm

The key idea here is that tickets have relative priority inside a particular context. So, we can keep an ordered list of ticket id's on that context object (in our case, the milestone).

On the milestone ticket list page we add a drag target and allow resorting of tickets via that target. We save that back to the server and store it on the context object.

When displaying a milestone display by "sort order" but filter out any tickets that aren't in the display (and update the list at that time).

Tickets that have that milestone, but aren't prioritized should be displayed in a separate "unprioritized tickets" section.


  • Mark Ramm

    Mark Ramm - 2010-10-04
    • custom_field__size: --> 4
  • Mark Ramm

    Mark Ramm - 2010-10-27
    • custom_field__size: 4 --> 4
    • custom_field__milestone: nov-01 --> backlog
  • Mark Ramm

    Mark Ramm - 2010-11-15
    • custom_field__milestone: nov-22 --> backlog
  • Tim Van Steenburgh

    I want this. Having tickets prioritized within a milestone is valuable. It allows the product owner to control what gets done first, and simplifies the ticket-choosing process for developers. Instead of scrolling through the list looking for an appealing ticket, you simply take the one at the top of the list.


Log in to post a comment.