Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-749

Add a setting to modify the initialization of JIRA Software ranking

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Hi,

      We recently use jira and greenhopper in our project and we are facing a difficulty. We use the greenhoper ranking to prioritize the issue. The queue/line of issues provided by greenhopper fulfill our needs except on one point, the initialization.

      When a new issue is created, currently the issue is put in the last position of the queue. However, it could be usefull is there is a rule on creation to help greenhopper putting the issue on the right position.
      For example, in our company, we would like that the issue is put on the queue according to the following criteria :

      • the priority
      • the creation date if the priority are equals
      • if priority and date are equals, the last created on last position

      This way, the first priorization is automatic and the managers just have to reorder the queue if needed but a huge part of the work is automatically made by the custom field.

      Is it possible to associate this kind of rules for the greenhopper ranking custom fields so that some fields could be used to calculate the initial order in the queue ?

            [JSWCLOUD-749] Add a setting to modify the initialization of JIRA Software ranking

            +1

            Nanuq Genome added a comment - +1

            +1

            How many votes are required to start working on it by Atlassian?

            Kacper Mazek added a comment - How many votes are required to start working on it by Atlassian?

            Want it to get bugs initialy ordered by the concept of "user pain".
            My initial rank would be defects (ordered by user pain) followed by tasks (ordered by due and priority).

            I would expect a new issue to get alligned on top of the greatest cluster of its kind.

            Marco Kinski added a comment - Want it to get bugs initialy ordered by the concept of "user pain". My initial rank would be defects (ordered by user pain) followed by tasks (ordered by due and priority). I would expect a new issue to get alligned on top of the greatest cluster of its kind.

            Liza Kuerzinger added a comment - - edited

            +1 Also needed here!

            Liza Kuerzinger added a comment - - edited +1 Also needed here!

            +1 Whats the hold-up ?

            Tim Ahrentløv added a comment - +1 Whats the hold-up ?

            +1 for this feature, it doesn't make sense to have new, high priority issues be ranked at the bottom of the list.

            Aiste Guden added a comment - +1 for this feature, it doesn't make sense to have new, high priority issues be ranked at the bottom of the list.

            Mihir Shah added a comment -

            Essential Item, its quite helpful.

            Mihir Shah added a comment - Essential Item, its quite helpful.

            Definitely need this! Not sure why it has been open for this long without being actioned!

            Manthan Patel added a comment - Definitely need this! Not sure why it has been open for this long without being actioned!

            I have the same issue, I need to be able to use this kind of filter query in Agile board (project = "X" ORDER BY priority, Rank ASC). I want every new created issue to enter the board at the bottom of the issues with the same priority.

            Georges Moubarak added a comment - I have the same issue, I need to be able to use this kind of filter query in Agile board (project = "X" ORDER BY priority, Rank ASC). I want every new created issue to enter the board at the bottom of the issues with the same priority.

              Unassigned Unassigned
              6cad095e5207 hugo lassiege
              Votes:
              121 Vote for this issue
              Watchers:
              72 Start watching this issue

                Created:
                Updated:
                Resolved: