Autoassign issues to next sprint when a Sprint is closed

[Ad Smeets]

One of our using team has very short spring and all issues that are created in the last two days will be added to the next sprints to start when current sprint is closed. issue creation is automated based on a mailhandler in Jira.

I tried to automate this in Automation for Jira and this should be possible. It will save the team a lot of work. Till now this does not work. I can select the trigger, create the conditon and then set the sprint. For some reson the condition gives me positive result, but when executing the rule it says nothing is found.

Has anyone created a rule for this purpose and is willing to share this?

[Nick Menere · Accepted solution]

Hi Ad,

This should be fairly straight forward and the rule will look something like:

Does you rule look similar?

What do you mean by "nothing found"?

Cheers,

Nick Menere

[Ad Smeets]

Hi Nick,

Thanks for the reply. I think my clarification was not complete. What I want to achieve is the following:

* Trigger: When a sprint is closed

* Condition: All issues that meet specific conditions (as an example status = new and labels = autoassign)

* Assign them to the next sprint

Below you find an example of one of the rules I tried to create. I tried more but the error message I get points tot the same cause. The message belonging to this rule is attached as well.

Question would be:

* Can I get the issues that meet the specified condition in the rule chain if the trigger starts?

* If yes, how to do this?

[Nick Menere]

Thanks for the Clarification.

What you are missing is branching on the issues in the Sprint. The Sprint Completed trigger doesn't act upon all the issues by default as you may want to do an action that has nothing to do with issues. E.g. just send an email.

To edit the issues in the Sprint, you need to explicitly branch on the issues in the Sprint.

Hope that helps.

Cheers,

Nick

[Ad Smeets]

Hi Nick,

I managed to create the rule that works. The issues that have to be added to the next sprint are not in cuurent sprint but still on the backlog.

The rule is quite simple, but I know now how I can select issues and get them in the rule chain so that's great. Now I can finetune to the selection criteria.

Thanks for helping me out. I can save this team a ton of manual work.

[Nick Menere]

Awesome to see you got it working!

[Legna Garcia]

where can I get the Automation option in the cloud version?

I have closed sprints with open issues :( I want to avoid this again.

[Nick Menere]

Hi Legna,

Automation for Jira is an addon that can be installed from the Atlassian Marketplace.

It comes in 2 different versions:

• Automation Pro - this is a paid add-on that has no limitations
• Automation Lite - free add-on with all the features but limited to 300 rule executions per month after the first 2 months.

If this sounds like it is what you are after (your use-case is common one for us) I'd recommend installing the free version and see how you go.

Cheers,

Nick Menere [Automation for Jira]
Co-Foudner

[Legna Garcia]

Hi @Nick Menere, thanks! 

when you say "300 rule executions", this means up to closing 300 sprints per month? or 300 stories that should be moved to the next sprint? 

Thanks in advance!

[Nick Menere]

Automation for Jira uses rules to execute logic/automations. In our free version you are restricted to 300 executions of these per month, no matter what they do.

So If you had one rule that closed issues on Sprint close - you could close 300 sprints a month!

Hope that helps.

cheers,

Nick

[Legna Garcia]

Thanks @Nick Menere, yes I just want to move open issues to the next sprint when closing a sprint.