How to fix Jira DataSync error codes – 400, 401, 404 and 500

 Below is a summary of the different error codes and the solution. Full details about each error are below the table.

(400) Bad Request.' summary":"Field 'summary' cannot be set.

This error may refer to the Summary that is not correctly mapped for the relevant artifact.
Please make sure that you have:

1. Used API key in Password field;
2. Jira Data Synchronization Configuration Helper tool (download link);
3. Completed Standard field mapping for {Artifact};
4. Set on the Auto Map users toggle button for this time.

If the error still appears in the Event Log, log a ticket with our support system with full details about the error message.

(400) Bad Request. {"errorMessages":[],"errors":{"rankBeforeIssue":"expected Object"}}

This error is mostly caused by having a Priority field not defined in the data sync for some products.
We recommend you to try to set the Priority (not a custom field, but Jira default field) in Spira, do not leave that field blank.

(401) Unauthorized.' Details: Basic authentication with passwords is deprecated’

As the error says, there is an issue with deprecated passwords, because Atlassian switched from passwords to API keys.
Please make sure you are using a valid Jira login and API key. Read more about this particular issue.

(403) JIRA REST API: 'The remote server returned an error: (403) Forbidden.' Details: Basic auth with password is not allowed on this instance

You need to enable basic authentication inside JIRA for accessing the JIRA REST API on this instance.
Or use Jira API key instead - [KB:464] Integration with Jira Cloud - Atlassian has depreciated use of passwords

(403) Forbidden.' Details: {"errorMessages":["No Link Issue Permission for issue

This message means that the user connecting to JIRA (datasync user from SpiraTest) does not have permissions to add links between issues in JIRA.
In case you're not able to do that, ask Atlassian support to assist you.

(404) Not Found

404-Not Found error refers to Jira server URL that you have configured in Spira.

Please verify that the url is correct and does not have slashes at the end.

(404) Not Found “Project with Key ‘KEYNAME’ either does not exist or you do not have permissions

This can happen when you have an incident in Spira that is mapped to a Release in Spira, but that release does not yet exist in Jira (or does exist but was created manually and is not synced with Spira).
Ideally, the synchronization user should have permissions to create new Versions/Releases in Jira. You can map all incidents in Spira to just one "dummy" release and manually link that to it in Jira so that Jira doesn't reject the incidents.

Read more about versions in Jira.

(404) 'The remote server returned an error: (404) Not Found.' Details: {"errorMessages":["Issue Does Not Exist"]

For more details please check our KB687 - Jira Server 9.0 and Later Breaking API Changes article.
https://confluence.atlassian.com/jiracore/createmeta-rest-endpoint-to-be-removed-975040986.html

(500) Internal Server Error

Error 500 – Internal Server Error refers to Jira internal error, so our recommendation is to pass this error to Atlassian support - this is outside the scope of what we can help with.
Please check your Jira application logs as they should give more information that will help you get assistance from Atlassian support.