By creating new sprint a new story is created in THIS new sprint (automation)

[Jeroen Kotterlink]

HI all,

I'm creating an automation that when I create a new sprint, a new story is created in this sprint.

I already managed to do this, but when I create a new sprint again, the new story is not created in the new sprint but in the first created sprint after the active sprint. 

How can I create this in the new created sprint? I tried several routes in "automation" but so far I didn't succeed.

I hope you can help me. 

Thnx.

[Karen Davis · Accepted solution]

Hi Jeroen,

I encountered a similar situation recently, and this article helped me immensely; https://www.adamnengland.com/2021/01/26/jira-automation-populate-your-sprint-with-stories-on-creation/. I hope it helps you as well.

Karen

[Jeroen Kotterlink]

Thnx Karen, it works.

[Bill Sheboy · Accepted solution]

Hi @Jeroen Kotterlink -- Welcome to the Atlassian Community!

Would you please post images of:

• your automation rule and
• of the audit log details, showing the case when the created issue is added to the incorrect sprint? 

That will provide some context for the community to suggest ideas.  Thanks!

I suspect you are getting the sprint information (for the issue create) from JQL rather than from the triggering sprint created.  The images will help confirm that, and what to update for a fix.

Kind regards,
Bill

[Jeroen Kotterlink]

When I create a new sprint, the first sprint after the active sprint is filled with the new created story. As soon as I create another sprint, the new story is not created because it checks the sprint after the active sprint, this one is not empty, so create nothing. But it had to create a story in the latest and empty sprint. 

I'm missing JQL experience to solve this, I guess.

[Bill Sheboy]

Thanks for that information.  If I understand your case correctly, you want to automatically add an issue when the sprint is created.

Using the trigger of sprint created, you should not need to perform any additional tests as the sprint will be empty if just created.  Perhaps try this:

• trigger: sprint created
• action: create issue, assigning it to the new sprint with {{sprint.id}}

[Jeroen Kotterlink]

Thnx, it works