Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Automation to move issues to backlog

Hello!

I want to build an automation in "Next Gen":

At the end of the sprint move all the issues with a certain field filled in to backlog. And the rest of the issues move to the next sprint.

When building an automation, I couldn't find the action to move issues to backlog, I only see the transition between the statuses in the workflow. Does the action exist?

Thank you in advance!

 

 

2 answers

1 accepted

2 votes
Answer accepted

Hello @yuliia_soury 

Currently it is not possible to use automation to move issues between the board and the backlog in Team Managed projects. Refer to this issue:

https://jira.atlassian.com/browse/JSWCLOUD-21481

 

@Jack In Team Managed projects, Backlog vs. Board is not based on the Issue Status.

Thank you for your answer!

Is it possible to use an automation to move issues between the board and the backlog in the Company Managed projects ("Classic")?

In a Company project being displayed in the Backlog list on the Backlog screen is about the status of the Sprints that the issue has been added to.

In a Company Managed project, an issue appears "on the board" (the Board view where there are columns of issues) when it is within an Active Sprint. If it is in a Sprint that has not yet been started, then it shows in the Backlog screen in that Sprint. If it is in a Completed Sprint but is not yet in a "done" status, and is not also in an Active or Not Started Sprint, then it will show in the Backlog list on the Backlog screen.

There is some Automation available to assess and manipulate the Sprint value for issues. However, I don't think you can set a trigger that would activate when you use the Complete Sprint action, and divide the incomplete issues automatically between the backlog and the next sprint. The trigger would activate after the sprint is actually closed and the issues have already been moved by the selection you make during sprint closure.

Like # people like this
0 votes
Jack Community Leader Jun 17, 2021

Disclaimer I have not tried this in TMP.

your backlog is defined by a status so I think that you would simply change the status of all incomplete issues to your backlog status. To differentiate those moved into the next sprint versus simply the backlog you would just want to set the sprint field for those that should be in the next Sprint. The challenge or rather question I have is how you determine the next sprint so you can actually set it in the sprint field.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
Community showcase
Published in Jira

⏰ Day in the life of a Jira Admin!

Hello Community! We thoroughly enjoyed this just-for-fun conversation in the Jira Admin Group about what it's like to be a Jira Admin. For #JiraJuly, our talented designers created these graphics t...

863 views 2 22
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you