Error Adding SpiraTest Incident to JIRA: An item with the same key has already been added

This error usually happens when you have the same Jira custom field ID mapped to multiple Spira custom properties.

Verify that you don't have more than one Spira custom property mapped to the same Jira custom field and remove one, when found.

Unable to locate mapping entry for {artifact} type X in project Y

When the sync process is activated from Spira, but the mappings have not yet been completely configured, the system does not know what to do with most artifacts and custom fields.

To start the mapping procedure, you need first to obtain the IDs.
Jira Configuration Helper Tool will help you with that, here is the download link.

Please note that the status, type, priority and custom property mappings do NOT support comma-separated values, you need to map to a single value only

Data synchronization is not enabled for project PRX and data sync system Y

Verify that the product you've configured the sync for is Active. To do this, navigate to Data Synchronization under the General section of the Admin menu and then click on View Product Mappings.

Unable to locate mapping entry for Jira user

This error means that there is no user in Spira that has a matching Jira Datasync ID for a user.
You can ignore this warning or create the users in Spira and then map them to Jira. That would also allow fields like the Owner/Assignee to be sync’ed in both systems.

Follow this link to find how to map a user in Spira.

Could not load file or assembly 'JiraDataSync' or one of its dependencies. (on-premise)

  1. First, right-click on the JiraDataSync.dll and choose Properties.
  2. Then check if there is Unblock the DLL is active. If yes, please check the box and do the same thing for the NewtonSoft.JSON.dll as well.
  3. Finally, verify that the plugin name is set according to documentation.

Error Adding SpiraTest Incident to JIRA: An item with the same key has already been added.at System.ThrowHelper.ThrowArgumentException

That error usually happens when you have the same Jira custom field ID mapped to multiple Spira custom properties.

Error: Exceeded data-sync plugin license count (1) for this instance

This kind of error is thrown when multiple plugins are used for the same source (second JiraDataSync for cloud instance).
If you'd like to sync two Products from Spira with different projects in a single Jira instance using same base URL/credentials, you do not need to create a the second DataSync entry, e.g. second datasync engine.
If you are syncing Spira to different Jira instances (different base URL/credentials), then you will likely need to an additional data sync engine available.