Jira automation error on publish

[Cathy Littell]

I am getting the following error "Something  wen wrong -- try that again" when I try publish my autiomation rule.  I am trying to set the sprint to the active sprint.

[Cathy Littell · Accepted solution]

The error has been resolved.  The board had multiple projects.  Not all projects on the board were scrum projects.  When a new board was created with only the one project and the new board was used to set the sprint to the active sprint the automation rule was able to be saved and published.

[Jack Brickey]

Hi Cathy, welcome to the Community. First might I ask if "To Do" is your initial status on create. If so then unsure why you would have the "Then: Transition the same issue to To Do" step. Aside from that commentary, are you able to publish if you leave off the last step - And: Edit issue fields? In other words is the issue w/ the final step?

[Jack Brickey]

another commentary - it seems that you are wanting to place all newly created issues into the Active Sprint. This is a bit abnormal at least in the agile-world where issues go to the backlog to be triaged and planned into sprints.

I'm just trying to understand your goals so that I might assist in finding a solution with you.

[Cathy Littell]

Initial status on create is open.  yes I can publish without the last step of setting the sprint.

[Cathy Littell]

I do not want all new issues placed in the active sprint.  Only those issues with an issue type of "Test Error - Dev"

[Cathy Littell]

As a side note.  If I change the last step removing the sprint from choose field and put the following in additional fields

{
"fields": {
"sprint": 49}}."

I can publish the rule and the rule works.   Obviously I don't want to hard code the sprint.

[Jack Brickey]

ok thanks for that info. So I haven't actually used Sprint in an automation but I just ran a quick test and it worked just fine. So let me ask....

• do you currently have an active sprint? i would assume that would need to be the case.
• i wonder if the automation doesn't have manage sprint permissions thought would not think that was the issue but...

[Cathy Littell]

yes I have an active sprint.

Project Role (atlassian-addons-project-access) has both schedule and update issue permission.