Duplicate key error on load - Easy Agile User Story Maps

This error is caused by JIRA Software upon creation of a Sample Scrum Project. A field is added to multiple tabs on a screen, which JIRA does not permit. And when you load the story map for one of those projects an error is encountered.

If you see the error "500 - Duplicate key com.atlassian.jira.rest.v2.issue.FieldMetaBean" it means that there is a duplicate field on a screen. To remove it, follow the steps below:

  1. Navigate to JIRA Administration > Issues > Screens
  2. Look for the Screen mentioned in the SQL query result e.g. "SSD: Scrum Default Issue Screen"
  3. Click Configure and look for the field e.g. "assignee"
  4. Remove one of the fields from the screen.

 

*In case there are mutiple tabs, check for each tab whether the field is called twice

 

More details can be found in this JIRA Knowledge Base article: https://confluence.atlassian.com/jirakb/createissuemeta-returns-duplicate-key-error-872016885.html

 

0 comments

Comment

Log in or Sign up to comment
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

247 views 1 3
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you