Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-11763

Ability to use sprints when backlog not sorted by rank

XMLWordPrintable

    • 13
    • 13
    • Hide
      Atlassian Update – 21 December 2018

      Dear Jira users,

      We’re glad to announce that this issue will be addressed in our upcoming 8.0 release.

      You can find more details about our 8.0 beta release here — https://community.developer.atlassian.com/t/beta-for-jira-8-0-is-up-for-grabs/25588

      Looking forward to your feedback!

      Kind regards,
      Syed Masood
      Product Manager, Jira Server and Data Center

      Show
      Atlassian Update – 21 December 2018 Dear Jira users, We’re glad to announce that this issue will be addressed in our upcoming 8.0 release. You can find more details about our 8.0 beta release here — https://community.developer.atlassian.com/t/beta-for-jira-8-0-is-up-for-grabs/25588 Looking forward to your feedback! Kind regards, Syed Masood Product Manager, Jira Server and Data Center
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Original summary Ability to use right-click "Add to Sprint" for issues in a backlog sorted by something other than rank

      Although it is currently possible to change the filter on a rapid board to show the backlog sorted by something other than "Rank", doing so completely locks the backlog so that you can't change the order OR move backlog issues into the current sprint.

      I understand completely why the backlog ranking is locked in this case and am not asking you to change this behaviour.

      What I do want is to be able to Right-Click on an issue in the backlog and "Send to Current Sprint".when the board is sorted by anything other than rank.

      This would allow me to view and assign issues to the sprint during sprint planning while using a view that is based on my idea of priority (i.e. business value), but would not require any changes to the default rank mechanic.

      This simple change would save me hours! Dragging and dropping issues to sort them in a list of several hundred items is just not workable.

            [JSWSERVER-11763] Ability to use sprints when backlog not sorted by rank

            Stanislav Natkovskyi (Inactive) added a comment -

            Hello rob.a.berube,
            depending on how you're fetching issues in an epic, yes, the order might have changed in the back end.
            What you could do in your script is to specifically tell Jira to order issues by Rank using JQL query.
            For example:

            "Epic Link" = EPIC-1 ORDER BY Rank ASC

            Hope this helps.

            Stanislav Natkovskyi (Inactive) added a comment - Hello rob.a.berube , depending on how you're fetching issues in an epic, yes, the order might have changed in the back end. What you could do in your script is to specifically tell Jira to order issues by Rank using JQL query. For example: "Epic Link" = EPIC-1 ORDER BY Rank ASC Hope this helps.

            Rob Berube added a comment -

            Did this change the way items are sorted in epics in teh back end? I had a script i was using that was fetching issues in an epic and then iterating through them. The order was based on rank but not it seems to be based on key. It's completely broken my script logic. help!

            Rob Berube added a comment - Did this change the way items are sorted in epics in teh back end? I had a script i was using that was fetching issues in an epic and then iterating through them. The order was based on rank but not it seems to be based on key. It's completely broken my script logic. help!

            Stanislav Natkovskyi (Inactive) added a comment -

            This is going to version 8.0.0. Unfortunately, I can't tell the exact release date as it's not fixed yet. But I would say that we should not expect it earlier than mid of November.

            Stanislav Natkovskyi (Inactive) added a comment - This is going to version 8.0.0. Unfortunately, I can't tell the exact release date as it's not fixed yet. But I would say that we should not expect it earlier than mid of November.

            Bhupendra Singh added a comment - - edited

            @snatkovskyi, Could you please provide the approximate release date?

            Bhupendra Singh added a comment - - edited @snatkovskyi, Could you please provide the approximate release date?

            Stanislav Natkovskyi (Inactive) added a comment -

            This is resolved and awaiting release

            Stanislav Natkovskyi (Inactive) added a comment - This is resolved and awaiting release

            JiraTrainer added a comment - - edited

            Is there a way in Jira too have a 500 issue backlog sorted by Business Value, and Risk Value then based on the  below prioritization criteria display Jira with RISK and Business Values so that I can  moved priority items to Sprint 1?

            priority 1:  High Risk/  High Business Value

            priority 2:  Low Risk /  High Business Value

            priority 3:  Low Risk  / Low Business Value

            priority 4:  High Risk / Low Business Value

             

            JiraTrainer added a comment - - edited Is there a way in Jira too have a 500 issue backlog sorted by Business Value, and Risk Value then based on the  below prioritization criteria display Jira with RISK and Business Values so that I can  moved priority items to Sprint 1? priority 1:  High Risk/  High Business Value priority 2:  Low Risk /  High Business Value priority 3:  Low Risk  / Low Business Value priority 4:  High Risk / Low Business Value  

            Cody Addison added a comment -

            I was excited to find out I could sort my backlog by fixVersion and priority and then disappointed that I could no longer easily add issues to sprints, epics, and versions. Without this feature sorting by anything other than rank is unusable.

            Cody Addison added a comment - I was excited to find out I could sort my backlog by fixVersion and priority and then disappointed that I could no longer easily add issues to sprints, epics, and versions. Without this feature sorting by anything other than rank is unusable.

            Madura Rodrigo added a comment -

            When is this available in Server? 

            Now more than one year, it was in Cloud. 

            Madura Rodrigo added a comment - When is this available in Server?  Now more than one year, it was in Cloud. 

            Konstantinos Voloudakis added a comment -

            Any idea if this is coming to the server any time soon? It's so painful to have to sort the backlog manually

            Konstantinos Voloudakis added a comment - Any idea if this is coming to the server any time soon? It's so painful to have to sort the backlog manually

            Jamie Rosenfield added a comment -

            We really really need this feature. Managing large backlogs is nearly impossible without it

            Jamie Rosenfield added a comment - We really really need this feature. Managing large backlogs is nearly impossible without it

              snatkovskyi Stanislav Natkovskyi (Inactive)
              4e8d258a8c4b Mat Pemble (Adm)
              Votes:
              58 Vote for this issue
              Watchers:
              51 Start watching this issue

                Created:
                Updated:
                Resolved: