Could you please help to understand what is the reason for failing the automation rule?
Here is the log:
The following issues passed: IS-773, IS-774
No fields or field values to edit for issues (could be due to some field values not existing in a given project): IS-773, IS-774
Found multiple fields with the same name and type: .Severity (com.atlassian.jira.plugin.system.customfieldtypes:select)
I have checked and all these issues have the 'Severity' field.
Welcome to the community.
It seems that you have more that one field that is named severity.
So the rule don't know which one to update.
So you'll have to check your custom fields and rename the fields, so that there is only one severity left.
In our case, a new Service Management project automatically created a new custom field named Severity and associated that field with 2 of the screens in this new project.
We had to change that screen associations to the original "Severity" field and, after all was re-associated, delete that new custom field created by that new project.
Thank you for your comments, because they definitely helped to find the issue, and I hope this helps someone who faces the same behavior.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events