"Edit Issue" in Automation for Sprint Name Change Failing

[Andrew Manuele]

I am trying to create an automation that will trigger when an issue is assigned to a user. After doing some other tasks (adding a label, adding a comment) the final step is to change the sprint to the current active sprint (see photo 1 below). 

Seems like an easy task but the action fails:

After reading this article I can confirm that the actor has permission to edit the Sprint field and the Sprint field exists. What am I doing wrong?

Side note: If I add the following to the advanced fields I can get the sprint to change:

```

{
    "fields": {
        "Sprint": "156515"
    }
}

```

But I'm trying to have the "156515" be a dynamic value based on our current sprint.

[Bill Sheboy · Accepted solution]

Hi @Andrew Manuele -- Welcome to the Atlassian Community!

First thing, I am using Jira Cloud and not Server, and so I am unable to validate the things I suggest with your version.

That error seems to indicate the sprint is not resolving correctly, as if there is another sprint with the same name in your Jira site.  Is that the case?

Next, when making multiple changes to an issue in a rule, it is a good idea to put a Re-fetch Issue after the earlier edits.  This reloads the data before proceeding, and prevents potentially "walking-over" earlier edits.

I notice you are using multiple Issue Edit actions.  Why not perform both of those edits in one step?

Kind regards,
Bill

[Andrew Manuele]

Thank you Bill! Turns out my team started using a new sprint and I didn't know about it. Was pulling the old sprint. The above settings work now :facepalm

And thank you for the multiple edit actions in one!