Although most of our customers are using the Inflectra.ai native artificial intelligence functionality in our platforms, we also offer options for customers to use OpenAI hosted in Microsoft Azure as an alternative. This is useful for customers that are using Microsoft Azure rather than Amazon Web Services (AWS). In this article we provide the technical architecture information for integrating Spira and Rapise with OpenAI.
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.
When you integrate Spira with Microsoft Azure DevOps you might get error records generated in your Event Log, while all expected artifacts are being synced.
This guide explains the meaning of the error codes and possible causes.
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
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.