Automation newly failing: sprint not getting recognized as valid field

[Marty Palibroda]

I have automation that moves issues that in a particular sprint to the backlog if they get commented on:

Up until May 13th this automation was working, but as of May 21st it started failing.

The action is configured with 'edit work item' using the advanced fields":

{
  "fields": {
    "sprint": null
  }
}

Did something change to the allowable fields?

[Trudy Claspill · Accepted solution]

Hello @Marty Palibroda 

Welcome to the Atlassian community.

Have you tried changing the field name to "Sprint" in the JSON code?

It is possible that a new custom field named "sprint" (with a lower case "s") has been added to the system, making it not possible for the automation to determine which sprint field you are targeting. You could use the "customfield_12345" nomenclature to explicitly identify the field you want to edit.

[Marty Palibroda]

Thanks for the suggestion Trudy!

That still seems to fail: 

How would the customfield_123 nomenclature work? I thought Sprint was a standard field.

[Trudy Claspill]

What is the Project Scope specified in the Rule Details for this rule?

What are the Types of the projects that are within the rule scope? Get the project Type information from the View All Projects page under the Projects menu.

What is your level of access in this Jira instance? Are you a Project Admin? Are you a Jira Product Admin?

Use the information from this document to print out the information for an issue that uses your sprint field.

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

You should find an entry that looks something like this:

"customfield_10020": "Sprint"

Note that the number following customfield_ may be different.

Search the content for all references to "Sprint". If a Jira Admin has created another custom field and named it "sprint" you may find more than one listed.

After finding all the customfield_12345 identifiers associated with the field name "Sprint" search through the content for each of the custom field identifiers that you found until you find the one that contains data that you can match to your actual sprints.

In your JSON code replace Sprint with the customfield_12345 identifier that you have confirmed identifies the correct Sprint field for your issues.

If this rule is scoped to Company Managed Software project(s) and you are a Jira Product Admin, then you could also go to the Jira Admin Settings > Work Items > Custom Fields, find the Sprint field that is "locked" and get the ID from the URL that displays when you hover over the configuration options for the field.

 

[Marty Palibroda]

Thanks again Trudy! Using the customfield from that url fixed the issue. Appreciate it.

I'm not an admin. I'm still not sure why this changed but I'm happy its working again.