Jira Service Desk Automation Error - Found Multiple fields with the same name and type

[Sue Hannan]

Hi, I have created project automation on a number of JSD projects and one project is not working as it tells me that it Found multiple fields with the same name and type. I am getting this when I map a custom field (from JSD to my Jira Next Gen Software project). I noticed the custom field is being used in more than one Jira Service Desk project however, Jira should know to use the field value from my project for my projects automation. Correct? Now when I read it says with the same issue type, then it sounds like if one of the projects that shares the custom field should change the issue type then it would work? Any ideas?  

[nmenere]

Hey Sue, we have recently done a bunch of work around supporting multiple fields with the same name.

Would love to hear exactly what you are trying to do and see some screenshots of your rule. If we've missed a common use-case I'd love for us to hear about it.

Cheers,
Nick

[Nithin Reddy]

@nmenere -- I'm running into the same issue. I'm using Jira Service Management and I have an automation rule in my next-gen service project check the value of a field called "Impact". This next-gen field clashes with a custom field used by a classic service project. 

Here's the error:

> Found multiple fields with the same name and type

[Nithin Reddy]

I worked around this issue by converting the field condition to JQL condition

"Impact[Dropdown]" = Significant

[Nic Brough -Adaptavist-]

>Jira should know to use the field value from my project for my projects automation. Correct?

Actually no.  Fields all belong to all projects, unless you have specifically limited their "context" to a sub-set of projects (or issue types)

You'll either need to rename one of the fields, or go to Admin -> Issues -> Custom fields, find both and change their contexts to the right projects.