Setup proper Active sprint with Parallel sprints enabled

[Mateusz Przybyłek]

Hi,

We have enabled Parallel sprints in our Board.

Additionally we use Automation for JIRA to inject Bugs automatically into one of your sprint.

Unfortunately, the automation task selects the wrong sprint from two active ones in parallel.

How can we determine which sprint should be chosen?

[Bill Sheboy]

Hi @Mateusz Przybyłek 

Please post an image of your rule to provide some context for the community to suggest ideas.

The criteria you use to trigger creating the defect (bug) may provide what you need to find the sprint.  Seeing the rule and its conditions will help confirm this.

Thanks, and best regards,

Bill

[Mateusz Przybyłek]

Here you have

How to choose proper active sprint in Automation when two of them are active in parallel?

[Bill Sheboy]

Hi @Mateusz Przybyłek 

Thanks for that additional information... Now the question is how do you decide which sprint to put an issue into when multiple ones are running?  The automation rule can only select correctly when it has the same information/choice-making you use. 

For example, if you are running parallel sprints for two teams and your teams use Components to indicate "team 1" and "team 2", the rule could use Component to decide.  And, to successfully select the sprint the parallel sprints need distinct names.  If they cannot be distinguished by your criteria, what you ask may not be possible.

Thanks,

Bill

[Mateusz Przybyłek]

In my case all bugs jump info one of running sprints. But still I cannot choose which one in Automation. There is just option "Active sprint"

[Sam Harding]

Hi @Mateusz Przybyłek 

One way to achieve this would be to specify the sprint in the 'Addition Fields' JSON in the 'More Options' section. Here you can specify the exact sprint using its id. It would look like this:

More information on finding out your sprint id can be found here https://community.atlassian.com/t5/Jira-questions/Where-is-the-sprint-id/qaq-p/37947. 

The issue with this approach is that when you start new sprints, you would need to configure the rule to update the sprint id each time. This is unavoidable, as @Bill Sheboy says, there is not enough information about the selection criteria for the rule to determine which is the correct sprint to put it into without having that manually configured sprint id every time there is a new sprint.

Hope this helps

Sam