Recently (starting in March 22nd, 2022, but later for some customers) Microsoft removed support for TLS 1.0 and 1.1 endpoints. If you are using an on-premise version of Spira, or a cloud version that uses an on-premise data-synchronization utility, you may get the TFS error: TF400324
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.
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 Team Foundation Server (TFS) - part of Visual Studio Team System (VSTS) - only runs in 32-bit mode. Therefore when using our integration there are a couple of steps you need to perform.
When using SpiraPlan, SpiraTest or SpiraTeam with Microsoft Azure DevOps instead of a local installation of Microsoft Team Foundation Server there are a couple of differences in the integration configuration that you will want to be aware of. This article describes those differences.
When you integrate Spira with Microsoft Azure DevOps (formerly known as Team Foundation Server or TFS) you have the option of matching up the custom properties in Spira with the user defined fields in Azure DevOps. This guide explains how you get the 'system names' for custom vs. standard fields.
When using SpiraPlan, SpiraTest or SpiraTeam with Microsoft Visual Studio Online instead of a local installation of Microsoft Team Foundation Server there are a couple of differences in the integration configuration that you will want to be aware of. This article describes those differences.