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.
The following issues passed:WS-17
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)
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
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.
This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...
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