Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-75253

"Rank to top" and "Rank to bottom" should be shown inside of an issue type e.g.: TASK in the New Jira issue view

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

      Summary

      The option "Rank to top" and "Rank to bottom" should be shown inside of an issue type e.g.: TASK into the New Jira issue view.

      A scenario where should appear

      a) open an issue type e.g.: TASK >>  go to a ticket detail page in the old issue view
      b) click on the '...' menu AT THE TOP RIGHT
      c) see the options to Rank to Top and Rank to Bottom.
      d) switch to new issue view.
      e) open an issue type e.g.: TASK >> go to a ticket detail page in the new issue view.
      f) click on the '...' menu AT THE TOP RIGHT
      g) see that there are NO OPTIONS to Rank to Top and Rank to Bottom.

      Important: This feature request (JRACLOUD-75253) is not a duplicate of JRACLOUD-72983 because this feature request only considers the scope under the EPIC.

      Where this should appear

      • Old issue view, where these options appear with success.
      • Where this should appear into the new Jira issue view.

       

        1. screenshot-1.png
          screenshot-1.png
          330 kB
        2. screenshot-2.png
          screenshot-2.png
          430 kB

            [JRACLOUD-75253] "Rank to top" and "Rank to bottom" should be shown inside of an issue type e.g.: TASK in the New Jira issue view

            salamonp added a comment -

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

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

            Alexandre April added a comment - - edited

            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. 

            Alexandre April added a comment - - edited 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 

            Paul Maguire added a comment - 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.

            Dylan Harnsberger added a comment - 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.

            Anusha Rutnam added a comment - 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.

            Arthur Zonnenberg added a comment - - edited

            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.

             

            Arthur Zonnenberg added a comment - - edited 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.  

            Hi 043b6a577a1b, I'm sorry for the confusion caused by this issue being incorrectly identified as a duplicate and closed in the past.

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

            May I ask your source for this? I am checking internally but from my experience, this is not the case. As long as an issue is (re)opened, it is being tracked.

            All that said, I don't want the incorrect value in the resolution field to continue to cause confusion so I will need to briefly close and then reopen the issue to clear it.

            Anusha Rutnam added a comment - Hi 043b6a577a1b , I'm sorry for the confusion caused by this issue being incorrectly identified as a duplicate and closed in the past. 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). May I ask your source for this? I am checking internally but from my experience, this is not the case. As long as an issue is (re)opened, it is being tracked. All that said, I don't want the incorrect value in the resolution field to continue to cause confusion so I will need to briefly close and then reopen the issue to clear it.

            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

            Arthur Zonnenberg added a comment - 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! 

            Sandra Kinsella added a comment - 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.

            Anuradha Nagendran added a comment - 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.

              Unassigned Unassigned
              cfraga Caio
              Votes:
              83 Vote for this issue
              Watchers:
              58 Start watching this issue

                Created:
                Updated: