Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

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

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?  

2 answers

0 votes

>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.

0 votes
nmenere Atlassian Team Sep 28, 2020

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

@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

Screen Shot 2021-02-03 at 5.22.30 PM.png

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

"Impact[Dropdown]" = Significant

 

Suggest an answer

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

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

880 views 14 20
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