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.
By default, all projects are completely self-contained; artifacts in one project can only be linked or associated with artifacts in the same project. However, there is a way for the project admin to selectively allow other projects to access artifacts in the current project. (Administration -> Project Associations)
The cross-project functionality is being introduced gradually. As of Spira version 6.0, it applies only to requirements, test cases, tasks (SpiraPlan and SpiraTeam), and incidents.
This article explains how and where the artifacts from another project can be used.
A customer recently asked how to get a list of all risks across all projects within a portfolio. This article explains how to create such a report.
Sometimes when using our MS-Office Add-Ins (for Excel, Word and Project) on a new computer you will see an error message of the type:Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.Office.Tools.Excel.Worksheet'. This operation failed because the QueryInterface call on the COM component for the interface with IID ...This article explains the cause of these types of error and provides some common solutions
Most of the artifacts in Spira are "soft deleted", i.e. they are simply marked with a deleted flag, and can be recovered easily by a project administrator using the Project History Changes option to review the changes, filter by deletes and revert the change. However when a system administrator deletes a whole project, it physically deletes the project and cannot be undone.