JIRA Automation : Create Sprint trigger

Question

Im trying to get an interruption ticket to generate whenever a sprint is started (and some  sub tickets underneath).

I select "Sprint Started" as the trigger, and then the appropriate board for the team, (Badassodors)  but when run, I got an error:

Sprint does not belong to the required board. HCPSprint 2021.03.12

which isnt related to the team/board I selected.

So I added a regex specific to the board/sprint I want, ( XPP (\d{2}.\d{2}.(\d{1}|\d{2})) - .* ) and this last time, I got an error:

Sprint did not match the supplied regular expression.2021.02.26_ACM

where ACM is a totally different team.

I notice that the 3 different Sprint interruption tickets (for 3 different teams) that I setup, I  would get the 1st error above (the other 2 I havent setup regex yet), but always had a random other team/sprint in the error.

What am I missing to specify each team/sprint/board?
Thanks.

JIRA admin_ogfbk7 · Answer

Unless you only have certain sprints you want to trigger from on your selected board, you do not need a sprint filter.

A log is generated every time the automation triggers...so every time a sprint is started. It then checks to see if the sprint which triggered the automation was from the selected board. If it is NOT the board you selected, you get a 'no actions performed' log. This is correct behavior.

Try again with only the board selected and no sprint filter. Start a test sprint in the board and see if the automation triggers like it should.

Jim Kinter · Answer

AFAIK each team has its own board and sprints. Im on 2 teams personally (the main CloudOps Pod and the 1 product Pod that I am the S.E. for) and each uses its own board and sprints.
It almost feels like the automation is seeing any sprint starting and trying to run my rule against it. But then when we start the sprint for the team/board I have assigned to the rule, it doesnt work either.

frother · Answer

Hi Jim,

Thanks for getting in contact.

Do you share sprints across multiple boards? I believe there is a bug around this (AUT-2070).

I have linked this article to the ticket which effectively acts as a vote for getting it fixed.

Cheers,
Scott.