Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Automation fails because two fields in the system have the same name

I am trying to set a severity when multiple conditions exists. The automation validates successfully but fails when a ticket is created and fails to set the severity.

The problem is there are two fields in the system, one is a previous custom field we had created for severity and the other exists from JIRA Service management. I was wondering, what is the best way to fix the issue, by not purging the two severities.

Action details:

Issue condition

The following issues passed:WS-17

Edit issue

No fields or field values to edit for issues (could be due to some field values not existing in a given project):WS-17Found multiple fields with the same name and type: .Severity (com.atlassian.jira.plugin.system.customfieldtypes:select)

2 answers

2 accepted

0 votes
Answer accepted

@albert_pinto -

When setting up automation, you need to specify the which field that you want to use.  In your case where you have two fields with the same name, you may selected the wrong "Severity" field in your setup.  I would recommend that you should rename your custom field "Severity" to something else (i.e. "Issue Severity") to differentiate your custom field with JSM's system field.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

One severity is from the JIRA service management product & the other we use for all our internal tickets and it's current production type.The first one I can't because it's something that came from JIRA service management & I don't know what impact it will do to the Service management product. I am open to deleting the one for Service management. Please advice if you think that is reasonable.

I removed the duplicate severity type & it worked without any issues.

0 votes
Answer accepted
Dirk Ronsmans Community Leader Apr 20, 2021

Hey @albert_pinto ,

Could you maybe share how you are setting the value? Is this through the edit issue properties or are you passing a "advanced" json?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Service Management

Next level incident management in Jira Service Management

Hello Atlassian Community! We’re thrilled to announce some exciting changes to incident management in Jira Service Management Cloud, in order to give your teams extra muscle during incidents, and ...

1,490 views 20 12
Read article

Community Events

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

Events near you