We have had some customers looking to upload files to Spira using our REST API. This article provides some sample code.
If you are using our Excel 365 addin you may see the error message:
We Can't Load This Add-In Because We Couldn't Connect to the Catalog
The steps to take to resolve this are below
We had a customer that was looking for a more automated way to remove test cases from a test set. The good news is that our REST API makes this easy.
Spira allows custom property at the test step level. This functionality allows testers additional flexibility. When custom reports are designed, some customers prefer to show the custom property at the test step level. This article discusses how to structure the ESQL query to accommodate this need.
If you are a cloud SpiraTeam or SpiraPlan user and have been using TaraVault Git repositories, you may find that your existing repositories don't appear in Spira after the update to v6.7. This may be caused by an authentication issue that is easy to fix
We had a customer that was looking for a way to easily purge out a large set of older automated test runs that were no longer needed in their project to free up space.
There is not currently a built-in tool to do this, but we thought it might be useful to provide a way to do it using a SQL Server Agent Job.
We had a customer ask us what was the recommended way to enter mathematical equations into a requirement in Spira. There are a couple of options depending on several factors:
- You want to do it 100% natively in Spira, vs. using an external tool with Spira
- How complex the equation is
- Does the equation need to be editable after the fact
A prospective customer asked us to elaborate on the pros and cons of importing into SpiraTeam using either ReqIF or the DOORS importer plug-in?
When you use the Perforce Provider for Spira you may sometimes run into a Windows folder permission error. This is due to the Perforce API running as a specific user that does not have access to the Windows temporary profile storage area.
This document contains an overview of how to setup and configure SpiraTest, SpiraTeam or SpiraPlan in a load balanced web farm scenario. It contains links to additional information from Microsoft, and community resources related to the scenario.
During the upgrade of an older version of Spira v6.x to the latest version of Spira v6.x the installer logs the following:
Cannot insert the value NULL into column 'TASK_WORKFLOW_ID', table 'SpiraTest.dbo.TST_TASK_TYPE'; column does not allow nulls. UPDATE fails. The statement has been terminated. [System.Data.SqlClient.SqlException]
When you are running the import from HP / MicroFocus ALM into Spira, you sometimes come across error messages that look like the following:
Error "The field <RQ_USER_17> cannot be used with requirement type <Non Functional>"
Although we have comprehensive documentation published on our website regarding the Spira REST API, sometimes users need some additional examples. In this article we publish an example of how to record a new test run using our REST API.
One of the most common needs when using the Spira REST API is the ability to update an item in the system (e.g. test case, requirement, task, defect, etc.). This article explains how you can use the REST API to do this.
You may find that SpiraTest, SpiraTeam, SpiraPlan reports sometimes don't open on Google Chrome, but instead try and download instead, which can be annoying. This article explains the setting you need to change in Chrome to fix it.
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
You may come across a situation where the base URL of your Spira instance has changed and the embedded image URLs no longer match. This will cause a broken image to display inside the various rich text editors in Spira. This article explains how you can use SQL to do a bulk update of the offending URLs.
A customer recently had some questions about what synchronizes between Spira and Jira, so we thought that this article would help clarify things.
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.
For additional security, customers may want to limit who can access their cloud instances of SpiraTest, SpiraTeam, SpiraPlan, or KronoDesk to specific networks and IP addresses. This article describes why you would want to do this and how we support this.
Behavior-Driven Development (BDD) is an Agile software development process that encourages collaboration among developers, QA and non-technical or business participants in a software project. It encourages teams to use conversation and concrete examples to formalize a shared understanding of how the application should behave. This article outlines how you can use SpiraTest to manage BDD style requirements and test cases.
In version 6.2.1 of SpiraPlan, SpiraTeam and SpiraTest we have added a new reporting API that lets you access the reporting capabilities of Spira programatically.
Sometimes when you use Spira or KronoDesk and perform actions (e.g. assigning bugs, test cases, etc.) email notifications are not received correctly. This article provides some common reasons and solutions
The SQL Server Database Engine Tuning Advisor examines how queries are processed in the databases you specify, and then recommends how you can improve query processing performance by modifying database structures such as indexes, indexed views, and partitioning. This can be used by on-premise customers to improve the performance of their Spira and KronoDesk instances.
With a recent update to Google Chrome (v76), Chrome had the CSS engine was modified which would make the sidebar navigation folder tree to become unusable. This issue was resolved by Google with the release of Chrome 77
Sometimes it is necessary to move a SpiraTeam, SpiraTest, SpiraPlan, or KronoDesk installation to another server, without wanting to lose all of your data. This KB will guide you through the steps of transferring the install over, and optionally upgrading the application. This guide will walk you through the recommended steps when needing to move both the application and database to new servers.
Sometimes when running the Spira v6.0 installer to upgrade from v18.104.22.168 to v6.0 you get the following error:
Table or indexed view 'TST_ATTACHMENT' does not have a full-text index or user does not have permission to perform this action.
This article describes the cause and provides the solution
SpiraPlan has a range of artifacts. These are the building blocks of a product or program and contain all of their data. Each artifact holds different data and is used in different ways. For instance, requirements are one artifact, and releases are another. They work differently, and are not interchangable. There are artifacts to help you test, plan, track bugs and tasks, and more.
Sometimes you want a simple test execution report that includes the list of test cases, execution dates and raised defects, without all the ancillary information in the standard Spira reports. This article provides an example of such a report.
When you are installing SpiraTest, SpiraTeam, SpiraPlan or KronoDesk on a database server with a large 'model' database sometimes the install will fail because the initial Spira/KronoDesk database is not large enough to contain your model database. This article provides the solution
When you upgrade from v5.4 to v6.0, unlike previous versions of the upgrader, we don't delete the entire database and recreate it. The upgrader makes the changes to live database in-situ. However if you have missing foreign key constraints in the v5.4 database it can lead to bad data that breaks the installer.
When you upgrade from v5.4 to v6.0 upon opening a test case detail page you receive the error: "The 'TestCaseWorkflowId' property on 'TestCaseType' could not be set to a 'null' value". This article explains the cause and provides the solution
You can use the Spira Project Backup & Migration Tool to move projects between one instance of SpiraTest and another pretty easily. However there is a known issue that can sometimes occur if you have deleted custom properties.
Sometimes users have more complex LDAP configurations. For example, users may have two different "Base DN"s where the users are located. They want to know - if there a way somehow to define two different "Base DN"s ?
Many of our customers are using SpiraTest / SpiraTeam with their own in-house test automation framework. In this article we explain how you can use our REST API and/or our sample jUnit code to integrate your own framework easily with Spira.
If you have disabled TLS 1.0 and 1.1 encryption protocols on your IIS web server, you may run into issues accessing the web interface of Spira or KronoDesk from older versions of Windows and/or IE.
Sometimes you want to delete the sample users in SpiraTest, SpiraTeam or SpiraPlan. This article explains the steps for doing this in versions 6.4 and earlier.
Starting with version 6.5, there is an easier method: On the System Admin Home page, click on the button to delete all sample data and users.
When SpiraTeam or SpiraPlan is connecting to a Subversion (SVN) repository running on Windows Server, sometimes the Windows server will not close connections fast enough, causing the cache build to fail.
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.
This post shows you how you can migrate or downgrade a SQL Server database from one version to a lower or earlier one. E.g. 2016 to 2014, 2014 to 2012, 2012 to 2008 etc. This can be useful if you maintain a heterogeneous environment of SQL Server instances and you have a backup from a newer version that needs to be hosted onto an older version. This happens to us quite a bit when customers installed a trial on SQL Server Express (latest version) and we need to host it on one our cloud servers.
A customer asked us for some sample code that illustrated how you can retrieve a filtered list of test sets using the Spira API. This example includes sample code using the Spira v5.0 API.
When you integrate SpiraTeam or SpiraPlan installed on-premise with an external Git source code repository, Spira has to maintain a copy of the Git repository locally. Sometimes you need to refresh this Git repo manually if an update did not complete. This article explains the process
This article explains the process for making a backup image of your "on-premise" SpiraTeam (or SpiraTest, SpiraPlan) instance and preparing it so that it can be sent to Inflectra to host on our cloud environment. This can happen when you have been using SpiraTeam on-premise, but now want to migrate to the cloud.
This article explains what to do if you are attempting to execute a test set and get this error message: "There are no test runs in this pending set to be resumed."
Customers running Spira v5.0 or v5.1 may experience an issue where the system will let you create test case folders that point to one of their children as parent. This causes an infinite loop which will break the system. This article provides a solution to fix the issue (though we recommend upgrading to v5.4 to prevent it happening in the future).
A customer asked us this question:
My team is using SpiraTeam 5.4 as a storage vault for all software documents. The documents are placed in a specific project "System" that has been created for this specific purpose.
The documents are placed into several subdirectories: Requirements, Risks, Design., General, etc
Can we generate a report that lists the name of the document, folder, author, and current version.
One of our customers was reporting that their instance of our TestNG plugin was reporting a 502 Connection Reset by Peer error. We did some debugging with them, and the issue appears to be a bug inside some versions of the Java Virtual Machine (VM) itself.
Sometimes customers will contact us regarding questions as to why the execution status indicator of their test sets is not being updated (i.e. everything still looks as not run) even after running some of the test cases. This article explains why this might be the case and provides solutions.
When you are first using the SpiraTeam plugin for JetBrains TeamCity, you may run into the issue where the settings for TeamCity are not being saved correctly.
Sometimes when you try and run certain reports you may get an strange error message "The passed in report ID or report format ID does not exist". This message is unfortunately a red herring, and there is a different reason for this error.
Of the unique needs of a requirements and test management system when working in the Defense industry, specifically when designing, building, and testing mission systems, is the ability to link individual test steps to the requirements. This article provides you with a custom report to use to display such a traceability matrix.
If you have recently upgraded to Spira v5.x from an earlier version and get an error message saving artifacts that mentions 'XPKTST_ARTIFACT_CUSTOM_PROPERTY' then you may have some old artifact custom property records that are blocking the new item saving
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.
The custom reporting functionality in SpiraTest, SpiraPlan and SpiraTeam v5.4 (or later) includes the ability to write complex reports, joining various tables, using SQL aggregation (COUNT, SUM, etc.) functions and other advanced reporting features. A common needs is to display a list of artifacts (requirements, test cases, etc.) and join against the custom property definitions so that you get the custom fields displayed with the names of the value not just the IDs. This articles explains how to do this.
Within the standard reports included with SpiraTeam (Test/Plan), some words exist, such as the 3-letter month abbreviations. These items are in English, even if you have chosen a different language for your Spira user interface. The report templates can be edited to change these words to a different language. This article explains how to do that.
We had a potential customer that was looking to generate simplified test result reports from SpiraTeam that had more details for each of the executed test steps, with full size screenshots displayed, rather than the small table cells that are in the small reports. This article contains an example of such a report.
We have had some customers looking to upload files to Spira using our REST API. This article provides some sample code.
Many of our customers work in the life sciences and healthcare industries. They want to use cloud hosted versions of SpiraTest, SpiraTeam, or SpiraPlan, but they need to be able to control the updates and also be able to have a staging and production environment. This article explains the options we provide
Many of our customers are importing from other tools, such as HP QC, HP ALM, Microsoft Test Manager, TestRail, etc. We have convenient import tools for these products. However sometimes these import tasks can fail due to interruptions. This article provides some solutions
Customers sometimes contact us with questions about how the Releases and Iterations in Spira work, specifically what kinds of data (test status, task progress, etc.) roll up from an iteration to a minor release, and from a minor release to a major release. Also they want to know whether iterations are included when you filter by release. This article provides some clarifications.
An automated test case stores its test script as a standard document inside of the SpiraTest/Team/Plan application. To GET the current script using our REST API you need to make 2 calls: 1 to get the document ID and the other to retrieve the script itself.
With the establishment of the EU General Data Protection Regulation (GDPR), you now may need to find old SpiraTeam projects that are not active any more so that you can delete them and reduce unnecessary storage of personal data.
If you are using SpiraTeam and SpiraPlan on-premise, and are looking at our TaraVault cloud-hosted code management service, this article explains what TaraVault is, and how you can have the same functionality on Premise.
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 5.4, it applies only to requirements, test cases, and incidents.
This article explains how and where the artifacts from another project can be used.
The incidents in Spira are able to have customizable incident types, statuses, priorities and severities. This means that each project has unique IDs for the various attributes. Sometimes when you incorrectly load in data using our Excel Add-In, you can link incidents to attributes from other projects. This article describes the problem and the solution.
Some of our customers who have SpiraTest, SpiraPlan, and SpiraTeam installations wanted to know how you can remove the "News Feed" RSS widget from all users' dashboards since it was causing Spira to access the www.inflectra.com domain.
Some of our customers wanted to know that we delete the data in the SpiraTest, SpiraPlan, and SpiraTeam tables when we delete a project. This article outlines the approximate order in Spira v22.214.171.124.
When you install SpiraTest, SpiraTeam, SpiraPlan, or KronoDesk on premise, you have a choice in different ways to configure SQL Server. Every situation is different, but this article presents some recommendations.
By default, IIS web server allows for limited file size to be uploaded to the web server. For IIS 6 and IIS 7, the default maximum file upload size is 4 MB and 28.6 MB respectively. IIS 7 returns a 404 error (HTTP Error 404.13 - CONTENT_LENGTH_TOO_LARGE) if someone uploads something larger than 30MB. In order to allow for larger file size uploads, a few server changes are required.
Integrating SpiraTest, SpiraPlan or SpiraTeam with your LDAP or ActiveDirectory direcory server makes a lot of sense. It allows you to have a single user authentication system, with all logins and passwords centrally managed. Spira includes integration out of the box with LDAP and this article provides help for some common issues that we have come across.
Customers sometimes ask us for a simple Release Notes report that can be used to display the list of new features and enhancements / fixed bugs in a specific release. We use a report like that ourselves to generate the Release Notes for our products (Rapise, SpiraTest, SpiraTeam, etc.). This article describes how you can create a similar report yourself
SpiraTeam has been designed to work with a variety of different software development methodologies, including several different flavors of agile, waterfall and hybrid. This articles describes one of the more popular waterfall methods called the V-Model and gives best practices for how to use SpiraTeam on such projects.
With the latest version of SpiraTest, SpiraPlan and SpiraTeam, we have provided a simple button in the Data Tools section that lets you rebuild the database indexes using the same script that we published in KB10. However sometimes the database is so large that the execution takes longer than the 30 minutes allowed by the application, or you want more control over the fragmentation levels that trigger a rebuild. This article provides guidance and a more advanced script for power users.
In the standard reports that come with SpiraTeam, we have the 'Detailed' reports that are designed to include a primary artifact (e.g. requirements) and then include tables that display lists of related items (e.g. Tasks, Incidents, etc.). By default, we only show some of the fields in these tables. This article explains how to display the value of specific custom fields in the tables when you customize the standard reports.
This article explains the process for taking a SpiraTeam (or SpiraTest, SpiraPlan) backup image from Inflectra's cloud servers and installing it on a local "on-premise" instance of SpiraTeam. This can happen when you have been using SpiraTeam in the cloud, but now want to host it locally.
Sometimes, when troubleshooting complex issues with SpiraTest, SpiraPlan, SpiraTeam or KronoDesk, it's necessary for us to get some additional information to troubleshoot the issue further. For example, when we receive a report of performance trouble when using our cloud services, there are a lot of different factors that may contribute to the problem. To narrow down the cause of the performance problem, we need more data.
A workflow is a predefined sequence of incident statuses linked together by “workflow transitions”. Incident statuses and workflow transitions are highly configurable. This article gives an overview of workflow transitions.
When you display a graph in the SpiraTeam reporting page, you can download a graph as a CSV file. Some customers have asked about ways to get the data making a REST call. This article explains the components of the API.
We often get questions about how the attachments in SpiraTeam are stored, and what the relationship is between the X.dat files on the file system and the original filenames. This articles provides information on this.
Sometimes you want to create a new custom report with a list of fields from SpiraTest that includes the date that a test cases was executed or the date that a defect was logged, but you don't want to clutter the report with the time part. Alternatively you want to join two tables on a date-time field where only a date comparison is needed.
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.
When you install the Spira MS-Office Add-Ins to help import data into SpiraTest, SpiraPlan or SpiraTeam from Excel, Word or MS-Project the installer will check that you have the Microsoft Visual Studio Tools for Office (VSTO) pre-requisite installed. Sometimes if you have this already installed with a newer version it will prevent the install from completing.
When using rich text editors in SpiraTest, SpiraPlan, SpiraTeam or KronoDesk with Google Chrome 54, users are seeing spaces not being accepted.
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).
When running Spira or KronoDesk on certain versions of Windows, when using the Czech or Slovak culture settings (or using Server default when Windows is installed in those languages) you may get unusual formatted dates.
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.
As part of the v5.0 update to SpiraTest, SpiraPlan and SpiraTeam, we made major changes to the database structure to improve performance and usability as well as lay the foundation for v5.1, v5.2 and v5.3 due out later this year. Customers using custom reports
that relied on the old v4.2 database structure will need to modify their custom reports.
The symptom is that whenever a user tries to open an Excel format report in SpiraTest, SpiraPlan or SpiraTeam, the report will download. When the user clicks on it to open,
Excel opens but the area where the report should be is blank and gray. It affects all reports types in Excel format. Other formats (HTML, XML, etc.) work fine.
On-premise / self-hosted customers who have Spira installed on older versions of Windows (eg Windows Server 2003) may be using an old version of Internet Information Services 6 (IIS 6). IIS 6 can restrict by default which API verbs it allows throwing a 403.1 error.
A couple of our customers have run into a situation where the new font-based glyph icons that we're using in Spira 5.0 don't display. This is usually due to a configuration issue within IE itself, this article provides the recommended solution.
When you upgrade an older version of SpiraTest, SpiraPlan or SpiraTeam (hereafter referred to as Spira) from an older version to the latest version, the installer has to upgrade the application and database at the same time. This article provides some solutions to cases where the installer throws an error or fails to upgrade the database for some reason.
When opening the SpiraTeam MS-Excel 2007+ reports in MS Office 2010 or later you may get a message displayed - "The file you are trying to open 'xxx.xls' is in a different format than specified by the file extenstion". This article explains why this message appears and how to deal with it.
Sometimes when you are using the SpiraTeam Importer for IBM Rational DOORS, you will get a DXL Runtime Error. This article explains the cause and provides the appropriate solution.
When using SpiraTest, SpiraPlan, SpiraTeam or KronoDesk with SQL Server 2012 or later, you may occasionally have a situation where the ID for an artifact (test cases, incident, ticket) suddenly jumps by exactly 1,000 values (e.g. from 214 to 1214 instead of just incrementing to 215).
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
During the course of investigating a technical support issue for SpiraTest, SpiraPlan, SpiraTeam or KronoDesk , the need may arise to run a query against your Microsoft
SQL database. To do so, you will use Microsoft SQL Server Management
Studio. If you did not install this when you installed SQL, you can
install it from the original source.
When connecting from Spira or Krono installed on a separate application server to a remote SQL server, you may have difficulties connecting. This article describes the steps for making sure that your SQL Server can be accessed remotely.
Sometimes when using our SOAP or REST APIs there are constants that are useful for some of the filters. In many cases they are included in the build-in API documentation, but sometimes they are not listed. This article details some of the release/requirement ones that may be useful:
Ask the user to clear out their browser's cache of cookies and stored internet pages/content. After they do this and then close and reopen their browser, the issue should be resolved.
This usually just means that the restored database just needs to be linked to the existing database server login. This can be done by executing the appropriate SQL command listed below:
This is a common need, since you may have installed SpiraTest, SpiraPlan, SpiraTeam, or KronoDesk on a workstation to evaluate its capabilities and now need to install it on a production server for real use, but you don't want to lose all your existing data.
This article answers some common questions about which databases you can run SpiraTest, SpiraPlan, SpiraTeam and KronoDesk on, and where you can get them from.
You already know the advantages of us hosting your application in our cloud:
- Focus on managing your projects not hardware
- Flexible pricing and contracts by # users
- Backups and all maintenance handled by our staff
- Globally accessible using just a web browser
- Get up and running in minutes with no installations
- Choice of hosting locations (USA, EU, Canada, India, Singapore, Australia)
However you may have questions about our hosting service. This article provides important information about our cloud hosting services, including security, privacy and reliability information.
Our web-based products: SpiraTest, SpiraPlan, SpiraTeam and KronoDesk make use of the Microsoft IIS web-server and Microsoft SQL Server database platforms.
This KB article explains some of the more common error messages that can occur after installing one of our products and the steps to remedy them.
This article was written specifically for versions v3.0 - v4.2 of Spira and versions v1.x of KronoDesk.
One of the benefits of using Inflectra software is that you get unlimited upgrades for the first year and as long as you maintain an active service plan. This articles describes the process for upgrading your installation of SpiraTest, SpiraPlan, SpiraTeam or KronoDesk to the latest version. It also answers many common questions about the process.
This articles describes the process for backing up instances of SpiraTest, SpiraPlan, SpiraTeam or KronoDesk (hosted on-premise). The example is written using SpiraTeam, but applies equally well to SpiraTest, SpiraPlan or KronoDesk, you just need to change the database name in the SQL files.
It is a common need to be able to connect our products (SpiraTest, SpiraPlan, SpiraTeam and KronoDesk) to a mail server. If we are hosting it in our cloud, then we take care of this for you, however if you are hosting it yourselves, you need to connect Spira or KronoDesk to an SMTP mailserver. This article provides answers to some common mail questions.
Sometimes you have a situation where a user deletes an entire tree of requirements and you only know the ID of one of the child items and not the parent ID that was actually deleted. This KB article provides a query that lets you find all the deleted parents of a specific requirement.
If you install SpiraTeam or KronoDesk on Windows 8 or later, you need to make sure that the various IIS Roles and Features are installed. If not, you may find that various Menus don't display correctly or that the pages do not display any data. This article describes the features and roles that need to be included.
To save space in the various SpiraTest, SpiraPlan and SpiraTeam reports, the default report templates use the format xxxxx. Often times it will be required to display a different date format either across the entire report or in part of the report. This article describes how to change the date format in one of the standard reports by changing the XSLT template used to generate the report.
Sometimes you want to get a report of all the users in the system. The custom reporting system in Spira allows you to create a custom report of all the users. This articles describes the process for creating such a report.
Our Spira platform (SpiraPlan, SpiraTest, SpiraTeam) has powerful custom reporting capabilities that let you build custom reports using the Microsoft Entity SQL language. This article provides some pointers on writing such reports.
If you face performance issues with Spira or KronoDesk when the users use Internet Explorer 9.0, there is a known issue in ASP.NET 4.5 that can cause the client to disconnect and all subsequent AJAX calls do not get processed. This article describes the symptoms and the solution.
Sometimes to diagnose issues with SpiraTest, SpiraPlan, SpiraTeam or KronoDesk it is helpful to increase the logging level to log all trace activity in the system. This KB article describes how to enable this feature.
After upgrading to Spira v4.2, if you get either of the following error messages:
- 'Width' is not a member of type 'Inflectra.SpiraTest.DataModel.IncidentView'
- 'DisplayMode' is not a member of type 'Inflectra.SpiraTest.DataModel.IncidentView'
Please follow the instructions in the article to solve the issue that happens when you try and use a saved filter that gives this issue.
We are planning on adding the ability to email the entire user list of the system and/or the membership of a specific project through the Spira UI, but for now this article explains how you can use a custom report to get a list of all the email addresses of the users of a Spira installation:
This article describes how you create / modify the XSLT report templates in Spira to include embedded images without having to manually embed them in the artifacts. It uses the ability of the XSLT reports to have an <IMG> tag in the report template that references the attachment URL.
When you use our SOAP or REST web service APIs
you will often times want to retrieve a filtered list of data. This is done by using the RemoteFilter that
lets you query the list of requirements, test cases, tasks, incidents, etc. and pass in the field to be filtered. This article includes the list of standard fields that you can use in the RemoteFilter.
The web-based custom reporting system in Spira v4.1 (or later) is designed to let you easily change the layout and contents of the various reports (and to create your own reports). It works in a format-agnostic manner, so that the same templates and layouts can be used regardless of whether the final report will be in PDF, HTML, Excel or MS-Word format. However sometimes there is a need to modify the specific template used to generate a specific format (e.g. MS-Word). This article describes the process.
If you have an installation of SpiraTest, SpiraPlan, SpiraTeam or KronoDesk that displays a 404 page not found message on certain pages, it may be due to a configuration issue on the server preventing the URL rewriter from functioning correctly.
Sometimes when running the SpiraTeam v4.1 installer to upgrade from an older version of SpiraTeam (same also applies to SpiraTest and SpiraPlan)
you will get the error message:
You must install the Microsoft .NET Framework 4.0.30319
even though .NET 4.0, 4.5 or 4.5.1 is installed.
If you run one of our installation packages (.msi) and receive the following message:
A DLL required for this install to complete could not be run
Sometimes when installing our products
you get error messages during the installation and it's necessary to provide Inflectra support personnel with detailed trace/logging information so that they can better support you. This article describes the steps necessary to enable Windows Installer (.msi) trace logging.
Sometimes we get help desk tickets from on-premise customers regarding the performance of our web-based applications (SpiraTest, SpiraPlan, SpiraTeam and KronoDesk). Whilst every situation is different, this article provides some common best practices that should help having a high-performing system.
In v4.1 the status of requirements was changed so that requirements set to 'Completed' in v4.0 will now be shown as 'Developed' with two new statuses Tested and Completed available.
The custom reporting functionality in SpiraTest, SpiraPlan and SpiraTeam v4.1 (or later) includes the ability to write complex reports, joining various tables, using SQL aggregation (COUNT, SUM, etc.) functions and other advanced reporting features. A common needs is to display a list of artifacts (requirements, test cases, etc.) and join against the custom property definitions so that you get the custom fields displayed with the names of the value not just the IDs. This articles explains how to do this.
The new release of SpiraTest, SpiraPlan and SpiraTeam 4.1 includes the ability to write custom reports against various reportable entities. This article provides a list of the available entities:
If you are running Spira v4.1 and you have the situation where you cannot create requirements or use case steps, please read this article for instructions on how to fix the issue.
SpiraTest, SpiraPlan and SpiraTeam versions older than v4.1 and KronoDesk versions lower than v126.96.36.199 use a screenshot capture utility written using the Java development platform. This lets the web browser capture a screenshot and attach it to items in the system without having to first save the item. This article describes some issues using this applet and outlines the replacement plan we have implemented to use HTML5 instead of Java going forward.
Several users have asked -- if it is possible to extract all incidents logged in a SpiraTest sever no matter what the project is. Using the built-in Incident reports or Excel Add-In, you have to extract incidents for each project and then move into one spreadsheet however they wanted to know if it was possible to do this as one extract from within the tool.
If you have installed the MS-Office Add-In for SpiraTest, SpiraPlan or SpiraTeam and the necessary prerequisites (VSTO and the Primary Interop Assemblies if using the MS-Office 2003 Add-In) but it won't display the Add-In in your instance of MS-Excel, MS-Word or MS-Project, follow these instructions to help us troubleshoot.
This article describes the steps in integrating a hosted instance of SpiraTest, SpiraPlan or SpiraTeam with Atlassian's JIRA On-Demand (hosted). We recommend using our cloud hosted data synchronization service that means you don't need any special tools or downloads to use both products together. Let us do the work for you!
When using some versions of Java with SpiraTest, SpiraPlan, SpiraTeam or KronoDesk you may get the following warning message when pasting in screenshots or images:
When I click to paste a screenshot attachment, get Java security warning (see screenshot) which says " Block potentially unsafe components from being run? Application: appSupa Java has discovered application components that could indicate a security concern. Contact the application vendor to ensure that it has not been tampered with" with options to Block and Unblock. "The application contains both signed and unsigned code".
When attempting to drag and drop items to rearrange list pages, it does not work.
This knowledge base article describes how to connect to the SpiraTest, SpiraPlan & SpiraTeam 4.x SOAP web services using Java code. It assumes that you've generated the SOAP proxy classes using JAX-WS. If you need to download pre-compiled versions of the classes, they can be downloaded from this knowledge base article.
This knowledge base article describes how to connect to the SpiraTest, SpiraPlan & SpiraTeam SOAP web services using Java code. It assumes that you've either generated the SOAP proxy classes using JAX-WS or are using the pre-compiled ones attached to this KB article.
This articles provides the solution to the following error messages that you may receive in Spira if you have missing default project attachment types/folders for a project:
APPLICATION.Business.Attachment::Insert: Inflectra.SpiraTest.Business.ProjectDefaultAttachmentTypeException, Can't locate the default project attachment type for project X
APPLICATION.Business.Attachment::Insert: Inflectra.SpiraTest.Business.ProjectDefaultAttachmentFolderException, Can't locate the default project folder for project X
Since our MS-Office 2007 Add-In for SpiraTeam uses the Microsoft VSTO technology, it's limited to being installed for a single user on a given PC. However if you need to be able to have multiple users access it, there are some registry keys that you can manually add.
In situations where your SpiraTest, SpiraPlan or SpiraTeam server is located on a company network that does not have direct Internet access (and connects through a proxy server), some of the integration features of Spira may not work correctly:
- The weather widget on the My Page
- The list of recent builds if your Jenkins server is hosted outside your network
- The RSS feed widgets on the My Page
- Data synchronization with bug-trackers that are externally hosted
This article outlines the step necessary to tell the Spira server to use the proxy server for its Internet connections.
SpiraTeam uses Java (tm) for attaching screenshots to artifacts and for adding a user logo or avatar on My Profile page.
If a current version of the Java Plug-In is not installed in your browser, problems can occur. Depending
on your browser, the source of the problem may not be clear. For example, sometimes IE will report that
there is a problem with the page. This article explains how to update your browser's Java Plug-In.
When you need to embed an image inside the description of a requirement, test case, task, etc. you need to follow the process outlined in this article.
With the release of SpiraTeam 4.0 you can then have these images appear in the PDF, HTML and MS-Word 2003 format reports.
The new release of SpiraTest, SpiraPlan and SpiraTeam 4.0 includes the ability to write custom reports against various reportable entities. This articles provides a list of the available entities:
Sometimes after your instance of SpiraTest, SpiraPlan, SpiraTeam or KronoDesk is upgraded (or you upgrade an on-premise edition), the screen doesn't display correctly.
If you have upgraded from Spira v3.2 to v4.0 you may receive a Foreign Key violation error message when you try and create a new project. We have identified the cause and will be adding a fix to patch 003. This article describes an immediate workaround.
After upgrading from v3.2 to v4.0 you may receive this error message when you access the Reports home page on certain projects:
Cannot deserialize the blob of personalization data associated with the current page.
Parameter name: data [System.ArgumentException]
The serialized data is invalid. [System.ArgumentException]
Value cannot be null.
Parameter name: enumType [System.ArgumentNullException]
This article describes the solution to fix this issue.
The steps to perform when needing to move the database to another SQl Server, or when changing the DNS name of your SQL Server.
When installing Spira on SQL Server 2012 (any edition) using Windows Authentication, you may receive an error message "Cannot Create User" (or similar) during the installation. This is because of a configuration change in SQL Server 2012 (as opposed to earlier versions). This article explains the step needed to prepare SQL Server 2012 for installing Spira v3.x. Newer versions of Spira will not need this step as the installer has been updated.
Using SpiraTest, SpiraPlan or SpiraTeam versions v2.3 - v3.2 you can create custom reports that can be displayed in the Reports tab of the system. This article explains the process for creating such reports. Note that the reporting system is being updated in Spira v4.0 and these instructions will not apply to v4.0 or later versions of the system.
This article describes the process and steps for moving your SpiraTest, SpiraPlan or SpiraTeam database from one computer to another.
The article will refer to SpiraTeam, but it applies equally to the other products.
In SpiraTest, when you create a new custom property in the incidents section, they are disabled by default. Unlike other parts of the system, the incident tracker has a customizable workflow. This article describes the steps necessary to enable the new custom properties in the workflow (which will make the custom property enabled).
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.
We have many different plugins available for different bug-tracking tools (see http://www.inflectra.com/SpiraTeam/Downloads.aspx
) however there may be cases where you need to integrate SpiraTest, SpiraPlan or SpiraTeam with a bug-tracker we do not currently support. This article explains the process for writing such a plugin.
This article has a couple SQL commands that can be run to optimize database speed and performance. This article applies to on-premise instances only. If your instance is cloud-hosted, please create a Help Desk ticket.
This article describes the steps for importing data from an Excel spreadsheet into SpiraTeam. You can use this to import requirements, test cases, tasks, incidents and releases.
This articles describes how to write custom reports in SpiraTest, SpiraPlan and SpiraTeam. It also can be used to modify the layout and styling of the various built-in reports.
This information applies to the following versions of Spira:
When installing SpiraTest/Plan/Team or KronoDesk on a Windows 2008+ server, some of the controls or content in the application does not display correctly.
This article describes how to resolve the following error message that can occur on new installations of SpiraTest, SpiraPlan, SpiraTeam or KronoDesk when ASP.NET is not correctly configured. This message typically only occurs on Windows Vista, Windows7 or Windows 2008 Server.
HTTP Error 500.21 - Internal Server Error
Handler "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list.
This knowledge base article describes how to connect to the SpiraTest, SpiraPlan & SpiraTeam SOAP web services using Java code. It assumes that you've generated the SOAP proxy classes using JAX-WS. If you need to download pre-compiled versions of the classes, they can be downloaded from our website at: JavaSoap30Classes.zip
This knowledge base article describes how to connect to the SpiraTest, SpiraPlan & SpiraTeam SOAP web services
using .NET code written in C#. The code assumes that you're using Visual Studio 2008 or later and are using the newer .NET 3.0+ Windows Communication Foundation (WCF) "Add Service Reference" rather than the older .NET 2.0 ASMX web service client.