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 ?
- details
-
JSWSERVER-692 Set ranking values based on current sort order
- Gathering Interest
- is duplicated by
-
- Closed
- is related to
-
- Closed
[JSWSERVER-749] Add a setting to modify the initialization of JIRA Software ranking
Totally agree with Vedran Grudenic and Hans Boot here.
This kills productivity for people who have to manage large backlogs and don't want to do the excessive manual ranking every time new issues are created in the project.
In my opinion this ranking should be configurable, if possible per project or board respectively. That way global admins, project admins or board admins could configure their initial ranking themselves.
I also support the idea of manual overriding this by manually dragging the issue card to the new position.
Added +1 first, but not sure since there could be an issue which makes the new (not yet checked) tickets to look like they became most important in backlog, just by adding a new one.
1)
When creating a new issue I'd like to be able to set its rank using a drop-down-menu directly in the GUI:
- Rank to Top
- Rank to Bottom
2)
In the JIRA server options I want to be able to set the default rank behavior for new issues, "Rank to Top" or "Rank to Bottom".
I would then set my default to "Rank to Top" and have new issues show up at the top of boards/lists and not hide at the bottom where they are forgotten.
Nanuq Genome
added a comment - +1 
Francisco Silva
added a comment - +1 
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.
Looking forward to this feature. I often look at my Kanban board and would like all new tickets to appear there on the top. Currently, all new tickets appear at the bottom and there are higher chances that I can miss some.