How to Fix Failed to update JiraID : XXXXX - An item with the same key has already been added.

[#1]

The behavior described in this document is foundational to Jira Align, hence it can be noticed in both Standard and Enterprise editions, and it can’t be altered.

Objective

This article describes how to proceed when a Jira Align work Item (e.g. a Story or a Feature) is not syncing with Jira anymore, and the following error message can be seen in its audit log:

By External System on <date> <time>
Failed to update JiraID : XXXX - An item with the same key has already been added

Description

This error can be identified in a Jira Align Issue (Story or Feature) audit log when it tries to sync an Issue to Jira. It basically happens when we have two custom fields mapped with the same Jira Field ID in Jira Align, since it’s not possible to sync two values from Jira Align issue to only one field in Jira it breaks the sync, throws the error in the audit log preventing issues from syncing properly.

How to fix it

To fix the issue you must go to your Jira Align Connector and find and remove the double Jira Custom field Assignment in the Custom Fields area.

• Go to Jira Align > Administration or gear Icon right beside your profile picture

• Jira Settings > Jira Setup tab

• Now in the Custom Fields take a closer look for duplicates customfield_xxxxx mappings, like the example below:
  
  

• Note: If you don’t find duplicates here take a look in the Field management Tab

• Now you have found the duplicate, remove or adjust it according your needs

• Hit the Save button at the end of the page

• Try to sync your affected issues one more time

Notes

• In case you need further support, or the solution presented didn’t work, feel free to open a ticket with us