We recently announced the release of an updated MS-Office plugin for Spira v5.0 that makes use of the new API in Spira 5.0. However some customers still need the older MS-Office 2010+ plugin for older versions of Spira (v4.x).
This article is obsolete.Our Excel365 plugin can be downloaded from the Microsoft Store from the add-ins menu. More details about the Excel365 addin can be found here.
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.
As you move your web applications (such as SpiraTest, SpiraTeam, SpiraPlan, or KronoDesk) to newer encryption protocols such as Transport Layer Security (TLS) 1.2, you will need to make sure the client applications are configured to use the latest version of TLS. Specifically applications using Microsoft .NET may not use the latest version by default.
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.
As described in a recent article, Microsoft Dynamics has been going through major changes in the past year, there are now many different products that all bear the 'Microsoft Dynamics' brand, including older legacy tools such as Dynamics AX, NAV, GP, SL and CRM and the new Dynamics 365 platform which has different modules (Sales, Operations, etc.). This article helps you know which tool you have when you need help from our Rapise support team.