Sometimes when integrating Jira with Spira, you might receive errors that refer to artifact mappings, statuses, or even users. This can happen even if the synchronization status is marked as ‘Success’ and highlighted in green. In this article we have combined certain synchronization errors that might appear while configuring integration with Atlassian Jira.
SpiraTeam is designed to work on both 32-bit and 64-bit systems, taking advantage of the extra memory and power available if you have a 64-bit operating system. However Microsoft's Azure DevOps Server (ADO) also known as Team Foundation Server (TFS) - only runs in 32-bit mode. Therefore when using our integration there are a couple of steps you need to perform.
Sometimes during the Jira plugin configuration to sync with Spira, you might get an error that is not self-describing and the errors do not point to an obvious solution. In this article we provide guidance on how to resolve some common synchronization errors with specific error codes (400, 401, 404 and 500)
This article is kindly provided by one of our customers - Boris - who has been using the Desktop Data Sync and JIRA to integrate his on-premise JIRA instance with a cloud instance of SpiraTeam.
The plugins listed on our website for integrating with JIRA are compatible with the latest major version (5.0 at time of writing) of SpiraTest, SpiraPlan or SpiraTeam. This article provides older versions of the JIRA data-synchronization plugin for customers that are using older versions of Spira.
A customer recently had some questions about what synchronizes between Spira and Jira, so we thought that this article would help clarify things.
This article describes some basic troubleshooting steps that you should take when the data-synchronization service between SpiraTest and another bug tracker (in this example Jira, but much of this also applies to other data syncs) does not appear to work correctly.
In order to synchronize SpiraTest, SpiraTeam, or SpiraPlan with Microsoft Azure DevOps (ADO) formerly known as Microsoft Team Foundation Services (TFS) you may need the IDs of the Areas inside ADO. This article describes how you can get this from cloud instances of ADO where you do not have access to the database.
For performance reasons, Atlassian has made breaking changes to the Jira Server API in version 9.0 (and later). This means that is you are using the Spira data synchronization plugin for Jira Server, you need to download the most recent version from our website. This also affects Jira Data Center.
Note: this does not affect Jira Cloud.
When you are integrating Spira with Jira cloud (hosted by Atlassian) and Jira server (locally hosted) you need to to connect to Jira using a login and Jira API Key. Previously (prior to June 3rd, 2019) you could also use a Jira login and password, that is no longer allowed by Atlassian.
If you are integrating Spira (SpiraTest, SpiraTeam, or SpiraPlan) with Atlassian Jira, you may get this error message if you have not updated the integration for a while:
Basic auth with password is not allowed on this instance
One of the features of the Spira synchronization service for Atlassian Jira is that it automatically adds relevant links to the user story and issue pages in Jira to make it easier to navigate from Jira back to SpiraTest, SpiraTeam, or SpiraPlan. Some users have reported these links are no longer visible.
When you use SpiraTest with GitLab, the synchronization plugin synchronizes some fields unidirectionally and other fields bidirectionally. To clarify the details, this article illustrates which fields are synched and in which directions.
We provide the source code for a number of the data sync solutions we provide (eg Jira). This gives customers the ability to tweak the precise behavior of the sync to their specific business needs. The open source code does not run in isolation and this article explains how to make sure you have everything you need to build and test your custom code.