Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-850

DevOps Automation: Actions to prioritise or rank issues to the top of backlog, retrieve top issue from backlog

    • 0
    • 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.

    • Jira Software

      Summary

      Currently, there are no actions that allow you to update the Rank field of Jira issues, particularly to send an issue to the top on Backlogs or Sprints.

      Proposed solution

      A new action should be added to "Send to top" so that an issue can be ranked to the top of the list.

            [AUTO-850] DevOps Automation: Actions to prioritise or rank issues to the top of backlog, retrieve top issue from backlog

            jmcmunn added a comment - - edited

            Are we really living in 2025 and there is still no way to update the rank of a Jira ticket via automation?  So many good use cases listed here already...

            jmcmunn added a comment - - edited Are we really living in 2025 and there is still no way to update the rank of a Jira ticket via automation?  So many good use cases listed here already...

            Adrián Plaza added a comment - You should use this answer on this post as a workaround https://community.atlassian.com/t5/Automation-questions/Re-Re-Automation-How-to-change-issue-Rank-to-the-highest/qaq-p/2684374/comment-id/10284#M10284

            Dwayne added a comment -

            A component within automation to adjust rank to top of backlog, bottom of backlog, or relative to a selected ticket would be very helpful!

            Dwayne added a comment - A component within automation to adjust rank to top of backlog, bottom of backlog, or relative to a selected ticket would be very helpful!

            y.hddi added a comment -

            This would be a really handy feature to add to automation. However it should not only focus on a "Send to top" option, but also on a "Send to bottom" option within a sprint. 

            We like to move the stories/issues with the status Done to the bottom, but we have to do it manually at the moment. 

            y.hddi added a comment - This would be a really handy feature to add to automation. However it should not only focus on a "Send to top" option, but also on a "Send to bottom" option within a sprint.  We like to move the stories/issues with the status Done to the bottom, but we have to do it manually at the moment. 

            Arthur Roncey added a comment - - edited

            +1 - need a way to automate based on conditions the move of new tickets to the board from the backlog of a Team-managed project (Software Management)

            Arthur Roncey added a comment - - edited +1 - need a way to automate based on conditions the move of new tickets to the board from the backlog of a Team-managed project (Software Management)

            Marc added a comment -

            this is needed!

            Marc added a comment - this is needed!

            Our use case is that we want things to keep on moving in a sprint and not get stuck due to new priorities.

            So our todo lane is ordered by priority, but once an issue gets resolved it should move to the bottom of that column, so that the first resolved issue gets tested first and the last gets tested last.
            Then when re-opened it should move to the top of that column, so that issues that have been worked on will get continued before starting new issues.

            Once an issue is in progress the first time, it's done by the priority of that issue.
            If an issue actually gets more priority and needs to be tested first, people can always manually move it back to top.

            An automation would be really desired
            Rules we'd be adding;

            • Issue from in progress to resolved -> move to bottom
            • issue from resolved, testing, reviewing to open -> move to top

            Samantha Adrichem added a comment - Our use case is that we want things to keep on moving in a sprint and not get stuck due to new priorities. So our todo lane is ordered by priority, but once an issue gets resolved it should move to the bottom of that column, so that the first resolved issue gets tested first and the last gets tested last. Then when re-opened it should move to the top of that column, so that issues that have been worked on will get continued before starting new issues. Once an issue is in progress the first time, it's done by the priority of that issue. If an issue actually gets more priority and needs to be tested first, people can always manually move it back to top. An automation would be really desired Rules we'd be adding; Issue from in progress to resolved -> move to bottom issue from resolved, testing, reviewing to open -> move to top

            Mr. Gray added a comment -

            I second everything everyone has said. A way to "move issue" to a different location based on a field or other would be great!

            Mr. Gray added a comment - I second everything everyone has said. A way to "move issue" to a different location based on a field or other would be great!

            I work at John Deere and this typoe of automation option would help my teams a LOT.

            I would love to hear about this when released please:
            AnamiTatianadasGracasL@JohnDeere.com

            thanks!

            Anami Tatiana das Graças L added a comment - I work at John Deere and this typoe of automation option would help my teams a LOT. I would love to hear about this when released please: AnamiTatianadasGracasL@JohnDeere.com thanks!

            This would be super helpful for us. We have a lot of tickets that get submitted by various members of the company, and automatically sending them to the bottom of the backlog would keep the top of my backlog in nice priority order.

            Kellen Hawley added a comment - This would be super helpful for us. We have a lot of tickets that get submitted by various members of the company, and automatically sending them to the bottom of the backlog would keep the top of my backlog in nice priority order.

              Unassigned Unassigned
              lellis2@atlassian.com Belto
              Votes:
              263 Vote for this issue
              Watchers:
              89 Start watching this issue

                Created:
                Updated: