• 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.

            [JRASERVER-6482] Strict priority for all open issues

            Brett Ryan added a comment -

            I can't speak for everyone but some of us can't afford GreenHopper along with the JIRA license

            Brett Ryan added a comment - I can't speak for everyone but some of us can't afford GreenHopper along with the JIRA license

            Additionally, the ability to prioritize projects within Project Categories would be a great way for us to prioritize by separate departments. Thanks!

            Taylor allee added a comment - Additionally, the ability to prioritize projects within Project Categories would be a great way for us to prioritize by separate departments. Thanks!

            I've voted for this issue and am now watching it as well. Is there anything else I can do to push this along? This feature would be HUGE for our company. To add to this, though, we'd like the ability to separately prioritize overall projects as well via this drag-and-drop functionality. This would be in addition to prioritization of issues within projects, and then also prioritization of issues per assigned developer.

            Taylor allee added a comment - I've voted for this issue and am now watching it as well. Is there anything else I can do to push this along? This feature would be HUGE for our company. To add to this, though, we'd like the ability to separately prioritize overall projects as well via this drag-and-drop functionality. This would be in addition to prioritization of issues within projects, and then also prioritization of issues per assigned developer.

            Hi,

            Is there an estimate when this plug-in will be released / non-beta? This functionality is critical to out operation.

            Thanks!
            Charlie

            Charles Hammes added a comment - Hi, Is there an estimate when this plug-in will be released / non-beta? This functionality is critical to out operation. Thanks! Charlie

            Edson Sossai added a comment - - edited

            I would like to add my "blessings" on this request. This little add-on would more a huge improvement on my installation and even save the long life of JIRA on our company.

            We have many issues where same criticalities are assigned, but always have to go over a priorization process to define which one will take precedence sue to resources constraints. Unfortunately today i have all my issues/requests in JIRA, but must keep a separate control to knows what is the currnt one being worked and what would be the next one on the queue. This would improve tremendouslly my work and internal process.

            I guess if you look into either Netflix or Blockbuster movie queue manager you will see exactly how this feature would work.

            Edson Sossai added a comment - - edited I would like to add my "blessings" on this request. This little add-on would more a huge improvement on my installation and even save the long life of JIRA on our company. We have many issues where same criticalities are assigned, but always have to go over a priorization process to define which one will take precedence sue to resources constraints. Unfortunately today i have all my issues/requests in JIRA, but must keep a separate control to knows what is the currnt one being worked and what would be the next one on the queue. This would improve tremendouslly my work and internal process. I guess if you look into either Netflix or Blockbuster movie queue manager you will see exactly how this feature would work.

            We're using Enterprise 3.13. We would love to have this facility. Why don't Atlassian work this into the code Jira code, rather than a plug-in that may break when the core is updated? Scrum agile development is picking up popularity. A development team that loses it's task prioritisation leader board for weeks while a plug-in is brought into line with a new Jira version could be a catastrophic event for the project.

            Dave Furlani added a comment - We're using Enterprise 3.13. We would love to have this facility. Why don't Atlassian work this into the code Jira code, rather than a plug-in that may break when the core is updated? Scrum agile development is picking up popularity. A development team that loses it's task prioritisation leader board for weeks while a plug-in is brought into line with a new Jira version could be a catastrophic event for the project.

            I too am looking for the ability to rank issues. The plugin does not work for the release of JIRA I have so having the ability to rank issues is missing. I'm adding my voice to having this feature in an official release as it seems rather odd to not having it already there.

            Stephen Farrugia added a comment - I too am looking for the ability to rank issues. The plugin does not work for the release of JIRA I have so having the ability to rank issues is missing. I'm adding my voice to having this feature in an official release as it seems rather odd to not having it already there.

            Is work still going on on this plugin? We really like the approach this plugin has taken to ranking - it is very flexible.

            Like many others on this issue we are using scrum and we are in a position where most of engineering is now using another tool for their agile dev management. That other tool also contains defect tracking and I would hate to see us in a spot one day where they want to replace Jira solely with the other tool. Jira is a much better overall product but without the ranking it isn't meeting the needs of the organization.

            Agile is already big but getting even bigger - I think this is a very worthwhile feature to have.

            Amanda Shenon added a comment - Is work still going on on this plugin? We really like the approach this plugin has taken to ranking - it is very flexible. Like many others on this issue we are using scrum and we are in a position where most of engineering is now using another tool for their agile dev management. That other tool also contains defect tracking and I would hate to see us in a spot one day where they want to replace Jira solely with the other tool. Jira is a much better overall product but without the ranking it isn't meeting the needs of the organization. Agile is already big but getting even bigger - I think this is a very worthwhile feature to have.

            JC added a comment -

            This feature is now supported by GreenHopper.

            Cheers,

            JC added a comment - This feature is now supported by GreenHopper. Cheers,

            An alternative solution has been implemented on top of bbPress (bbPress.org) @ http://www.namastenetizen.com/sbbp/prio.php?tag=un

            Kishore Balakrishnan added a comment - An alternative solution has been implemented on top of bbPress (bbPress.org) @ http://www.namastenetizen.com/sbbp/prio.php?tag=un

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

                Created:
                Updated:
                Resolved: