Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-6482

Strict priority for all open issues

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • Issue - Fields
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Atlassian Status as of 7 Sept 2010

      Hello all,

      Thank you for all the comments and votes on this feature request.
      Since we now have GreenHopper and GreenHopper ranks issues very well we have decided not to include this feature as a core part of JIRA. That way we can concentrate on bringing other features to JIRA.

      I am resolving this feature request now as 'Won't Fix' and please don't hesitate to contact me directly if you have any concerns.

      Cheers,
      Roy Krishna
      JIRA Product Management
      roy at atlassian dot com


      For planning the work on open issues we need to set a strict priority for every open issue. That is, every open issue must either be more important or less important than every other open issue. It is not enough to set one of a finite set of priorities since we need to determine which issue to solve first even if both are Critical. These priorities are global per project. This way of strictly prioritizing issues is at the core of every agile methodology like XP, Crystal, and Scrum.

      If this can be done using custom fields or otherwise, please point me to where I can learn how to do it, or give a descripton here.

      Ideally I would like to be able to list open (or any) issues in a filter and get UP/DOWN arrows for every row to raise or lower the priority for this issue. Raising the priority of an issue (A) moves it one place up in the current list. The issue (B) shown directly above it before raising it ends directly below (A). Issues not shown in the current list that were between (A) and (B)are kept directly below (B). Vice versa for lowering the priority of an issue.

      TOP/BOTTOM buttons would also be great, but may be limited by graphical design or screen space issues.

      The permission to set priority could be associated with certain groups of users, in our case the CUSTOMER role.

      This issue is very important to us, and I hope you will give it serious thought.

      Another way of describing this priority system is ordinal priority.

              Unassigned Unassigned
              6376daa1b740 Uwe Kubosch
              Votes:
              121 Vote for this issue
              Watchers:
              66 Start watching this issue

                Created:
                Updated:
                Resolved: