This is still an issue for those who migrated from on-premise Jira instances to cloud. The missing feature is a major pain point.

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.

This is not true since this is a lost feature, not a new one. 

As project manager, I regularly have to adjust the ranking of a large number of items. Just now, I have to arrange 51 items in my backlog and badly miss the Rank to Top/Bottom feature that was available. I have tried exporting and importing the rank to no avail. I could see the rank field updating in the issue change history but the new ranking wasn't effective on boards or issue list sorted by rank 

Ok so this is still open? This is now EVEN MORE of a problem now that the old issue view is no longer available. It was literally faster for me to go through all of the clicks to get to the old issue view and then use the keyboard shortcut "." menu on the old issue view to rank the issue to the top of its column. Now the ONLY way to rank an issue is to go find it visually on the board, click and drag, or click and use "s"+"t" to send it to the top of the column. Why isn't this available within the issue view? Why was this functionality removed from the new issue view keyboard shortcuts? Super frustrating.

Thanks for this 043b6a577a1b. Let me talk to the team internally about how we can better handle the subtasks on JRACLOUD-70555 – New Issue View in Jira Cloud. I see what you mean now and agree that the green checkboxes + resolution field values on open issues are misleading. Thanks again for your assistance.

Hi Anusha, sure thing. If you go to the parent ticket https://jira.atlassian.com/browse/JRACLOUD-70555 , you'll notice something similar happening for https://jira.atlassian.com/browse/JRACLOUD-78471 . In the parent ticket, this subtask has a green checkbox:

https://imgur.com/LB2PXX7

The same thing was the case for this issue https://jira.atlassian.com/browse/JRACLOUD-75253 , the only difference being the Resolution was Duplicate instead of Fixed.

Now I see you've moved the subtask into a separate task, which is fine: as long as the feature gets restored. I agree https://jira.atlassian.com/browse/JRACLOUD-75253 is the same as https://jira.atlassian.com/browse/JSWCLOUD-20439 , but in different projects it seems.

I would like to remind everyone that all votes on this issue are ignored (because this issue got marked as Resolved as Duplicate at some point). Please make yourself heard in the parent issue: https://jira.atlassian.com/browse/JRACLOUD-70555

Another vote! 

This is a very important feature as it provides a simple way to Rank an issue. Looking into the backlog with projects having 100s of issues to put an issue to the top is cumbersome.

This is a productivity issue for me too. There seems to be no easy way to move a newly created Story in an Epic to the top of the backlog quickly and easily.

Please fix this before the old view is cutoff. This is a very important feature and will cause issues if you do not include it. Thank you.

I'm missing this option since we moved to the cloud version. Just voted in https://jira.atlassian.com/browse/JRACLOUD-70555* 

It cost me a lot of extra effort not having this function anymore.

another vote. please fix it.

Another vote from me, its really inefficient to stich back to the backlog to rank issues.

Perhaps we can better comment on the parent issue rather than this sub-task, because this sub-task was closed as Duplicate at some point. Re-opening it did not clear the .

*Parent issue if you think Rank to Top/Bottom is important to add inside the new issue view: https://jira.atlassian.com/browse/JRACLOUD-70555*

I really miss this ability to rank to top/bottom in the issue view. It's so much more convenient than having to to load the backlog, find the issue, and then re-rank it.  

Hello,

This is also important for us, please fix it.

Another vote from me, why this was removed is completely unclear to me but it is a huge pain... The whole new 'issue view' seems like a step back in my book. Both this and the missing edit button to edit all the non visible fields are extremely annoying...

Please can this be prioritised soon. Really painful not having this especially considering the old view had it. It's a regression in my book

This is a huge pain point. Every time you create a new priority ticket you have to manually drag it to the top of the board, which causes Jira to crash half the time. 

I use this every refinement. Not having it in the new view is a pain, I keep flipping to the old view to get it. My vote is to have it, am willing to pay for it

Every day this remains missing is a huge pain.

Ranking to top of backlog while in the view=planning.nodetail does not work if there is a subtask at the top of the backlog. The Rank to Top / Rank to Bottom options on issue view missing are still by far the most annoying thing about the New Issue View.

You can still access the old view with the three dots on the upper right corner or by adding ?oldIssueView=true at the end of your issue URL. It is just annoying to do this everytime since you can't have the old view by default.

The other work around I do is to open another browser showing my backlog and do a right click on the issue(s) to rank them to top.

Why is this still missing from the new issue view? Please allow me to have the old issue view until this feature is available. It is a critical part of my work flow. Thank you!

Hello, We were using the "rank to top" button in the issue view everyday. Now that we migrate to cloud we lost the functionality. Please consider this request to bring this feature back.

I have been forced to the New Issue View and yet this previously existing functionality is still missing from that view.

I've reopened the feature request JRACLOUD-75253 that was closed as duplicated because the customer mention this is a different scenario. We need to consider the below scenario, where the "Rank to top" and "Rank to bottom" should appear inside of an issue type e.g.: TASK as well. The feature request JRACLOUD-72983 only considers the scope under the EPIC.

A scenario where should appear

This request is already being tracked in JRACLOUD-72983. Please watch there for updates.

Thanks,

Jira Cloud Team

These ranking options on the (old) issue view menu are a critical part of my workflow.  I start the issue triage process based on a notification in email or slack that has the issue link.  From there I change the status to put it in a development queue or the backlog.  The 'Send to Top' feature allows me to get important tickets into the top of my Kanban queue, or the top of an epic member ranking immediately.  Without it, I would have to then go find the issue on the Kanban board (which could be anywhere in a column based on the ranking of the issue in question), and adjust it's ranking from there.  If there are a lot of issues in the given Kanban column (or epic members view from the Kanban Epic Panel), this is a frustrating process. 

If I'm doing this via mobile, it's even harder to find the issue because of the small screen size.  For less important issues, I'll still use the (old) issue view to 'Send to Bottom' feature so that I'm able to find them more easily, or just to designate they should be at the end of the queue.

Not having this feature would cost me substantial time every day, as I triage many tickets as they come in.  I would not willingly transition to the new issue view without this feature.  Considering you are expecting all users to transition to the new view, we shouldn't be losing functionality that was available when we selected Jira as our SDLC management system.