Automation rule failed

Question

Hi,

Could you please help to understand what is the reason for failing the automation rule?

Here is the log:

Action details:

Issue condition

The following issues passed: IS-773, IS-774

Edit issue

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.

joao.galvao · Answer

Same here.

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.

Bastian Stehmann · Answer

@Olga Shprygova ,

Yes, the field must be unique in the whole site.

@Anastasiia Shevchenko ,great to hear that.

Anastasiia Shevchenko_gpwgrh · Answer

Thank you, Bastian! 
I have renamed one field and rule passed.