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.

any update on this @Nicholas Muldoon ?

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.

 would be very useful

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.

+1

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.

+1 Also needed here!

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

Essential Item, its quite helpful.

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.

+1 for this feature as well. Currently using a lot of time dragging all the new issues to the top every time after creation.

Our company needs this feature as well.

I've had two clients request this sort of feature for the backlog. Some of their projects end up with near 1000 issues in them and when they create an additional one it plugs it in just below the issue they currently have highlighted.

The ability to create a custom initial sorting method based on various fields in the issue and then allow rank sorting after this would be a major improvement to the use of both Agile boards.

I Completely agree to Hans Boot on this.

Second here.

My problem:
The present situation gives me no oversight on the important issues. No good visual identification, no good ranking. With regards to productivity, I am sorry to say that us moving to Jira Agile has been a bad experience. I regret the move. Even Trac or Mantis give me better dashboards and therefore more productivity.

I understand the rationale behind "Rank", but one cannot have meetings on the ranking all the time. On the other hand, tickets do come in all the time, and especially the urgent and important ones need to be highlighted. However, the opposite happens now: no highlighting at all. Everything goes in one big heap without real means of distinguishing them. Forget that tiny icon of the priority please, I don't like seeking for needles.

Disregarding priority when ordering tickets is a very bad design decision that I do not understand. Upon ticket creation, we have the "Priority", so make use of it. I understand the need to have manual override later on, but upon creation the priority should have an influence.

My conclusion now: If a rank cannot be set upon ticket creation or if important/urgent tickets cannot be given some other good visual clues, I will remove the rank field and revert to priority sorting. If that is not possible, I'll remove Jira Agile.

Is there a reason why the board prevents us from dragging an issue to a sprint when Backlog is sorted using a custom filter? Is there even a way to include an issue in a Sprint in that case, using the Plan screen or any other screen?

I understand that once you use a custom filter, there can't be any additional manual reordering of backlog issues, but I thought that "moving an issue to a sprint" is nothing more than assigning its Sprint field. This seems like something that should easily be allowed, although I am pretty sure I am missing something crucial in the implementation. If none of this is technically feasible, it would at least be neat to have an option to choose whether new issues will be ranked to top, instead of getting the lowest rank.

Additionally, if nothing else, does anyone know if any of this can be hacked using one of the custom workflow plugins (e.g. JIRA Misc Workflow Extensions)? Something like, "on issue creation, set the Rank field of an issue to top"?

We would also like to see this. We have two separate agile boards for managing the same issues: one is a planning board for managing upcoming short-term and long-term goals, and the second is an "active" board for managing the current sprint and what's planned for the subsequent one.

Sometimes we need to move issues (via status changes) from the active board to the management board. When this occurs, we would like their rank to bring them to the top of the board, so that the issue doesn't get lost in the giant backlog of the management board. Currently this is a huge problem for us as it takes a great deal of time to find the old issue after it is moved.

We would like to do this via a workflow transition. What would be sufficient for us would be to have a workflow transition that just sets the rank of the issue to either the lowest or highest rank available in the project containing the issue.

I would like to have a way to implement a function like "IF priority == (BLOCKER or CRITICAL) THEN MoveToTop"

Same issue as others but I'll repeat anyway. When creating a new issue and we have many issues already in our queue, we need to scroll to the absolute bottom of the boards since new tickets are created by default with the lowest rank.

If I remember correctly, the old Classic Boards had a field when creating a new ticket for where to rank the ticket (top or bottom of the queue). Even something that simple would be better than what we have now: nothing.

We had a home grown ticket system that we implemented the override query above, seemed to work well allowing the rank to be readjusted based on above.
I guess if i created a custom field and used groovy to implement the calculation, we could order the backlog using that field

I see multiple requests for this across multiple tickets. There should be just default behaviors for ranking after ticket creation than can be changed. Can you give us an update when this ticket might be addressed? Thanks.

Same here.
We have a well sorted "backlog" and wanted to use the Jira Agile feature of "drag and sort" issues.
But it won't work since our order is based on several sorts and fields, not including the "rank" field.

Regards
Maik

Same thing here as previously said by other users, we just implemented GreenHopper and we already have a well prioritized backlog of many hundreds of items which we must now manually drag all over the board. Moreover, when someone enters a critical issue, it still sits at the bottom of the very long list and needs to be drag to the top even if its priority, severity and due date have all been set to make it highly critical.

It's becoming an issue that makes the implementation of GreenHopper a problem in our company.

I would like the ability for rank to work as follows:
Rank is updated based on up to X fields specified in a configuration setting. In my cases, PRIORITY, SEVERITY, and DUE DATE.
Assuming all three are required, it should work like this:
Rank = (( Value of PRIORITY * 100)+ ( Value of SEVERITY * 100) + (DAYS UNTIL (DUE DATE) * 10))
Example ticket 1:
Priority 2
Severity 2
Due July 13,2013
Rank is 420

Example ticket 2:
Priority 1
Severity 2
Due July 14,2013
Rank is 330

If someone moves the ticket in the scrumboard higher, or ranks to the top, it will set the rank and a flag called rank override, once rank override is on, if the fields change (PRIORITY, SEVERITY, and DUE DATE. ) it will NOT recalculate the the RANK

Agree, this is becoming a serious issue when you have a few hundred issues in the backlog with various priorities. What we're forced to do now is go to the Kanban board after creating a high-priority issue and manually rank it to the top, this is obviously a bad solution.

It cannot be done today but this is surely something we could implement.

Cheers,