Articles Tagged 'ide'

A customer asked is how they could run a report on a daily basis to see for how long a defect has been assigned to a specific status and the audit log of the status changes. That is best done by using the History table and the main Incident table together in a custom report

One of the frequent questions that the product or project teams face is knowing the number of risks across the risk breakdown structure.  This risks identified metric not only helps with the team's ability to ensure their commitments are met but also increase the confidence that the product or project team is managing the project effectively. This article addresses how to report this metric.

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.

This article is obsolete.
It is referring to the old bug fixed in later versions and applies only to that particular case when upgrading to Spira v4.2.

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).

This article is now obsolete.
Custom Properties are now always active and do not require separate activation.

A customer asked us how you could create a custom report that shows the following information in a single table:

• A list of test sets containing:
  • test cases
    • test steps
• For each test step, the linked:
  • attachments
  • incidents

When you are installing the Spira plugin for Eclipse on workstations running Eclipse 2022-12, sometimes it won't install because of missing/invalid dependencies. This article provides information on fixing this issue and also how to deploy the fixes for customers where their Eclipse instance is not able to download packages from the Internet.

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 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).

Rapise supports many types of objects in Web, Mobile and Desktop applications.  And each object has a set of actions that can be applied to it.  You may want to override behavior of existing action or add a new one. Learn how from this article.

A customer of ours asked for a custom report / graph for displaying the count of incidents by project and by priority.

In some cases a test may automatically determine that it's failure is definitely caused by a bug in software under test.  In this case the test may create an incident in Spira using Spira.CreateIncident action. Requires Rapise 7.2+.

We often get asked by our customers about the types and level of support we provide, as well as details on how we host their information (for cloud customers). This article provides an overview of our support, cloud hosting and the option to deploy on-premise.

Some customers may want to see the summary delivered outputs of their past releases. To do so, in this example, we create a custom report that shows a table of the total number of Incidents and requirements assigned to each past releases (releases with an end date in the past).

One of our customers asked us how to extract the defects/incidents linked to the blocked test cases in a report. This article shows you how to do this using a simple custom report.

A customer asked us if we could provide a report of all the incidents across all projects and programs. In SpiraPlan you already have a Program Incidents list page that shows this information.  However sometimes you want the information in a report format.

A customer asked is how they could run a report on a daily basis to see for how long a defect has been assigned to someone and the audit log of the assignment changes. That is best done by using the History table and the main Incident table together in a custom report

A customer asked us why Rapise uses Pascal Case names for the various operations, functions and properties, as well as the reason why operations are prefixed with a "Do" action name.

One of the metrics that customers often find useful is the number of times that a specific incident has been reopened. We plan on adding some built-in dashboard widgets for this metric, but in the meantime, we have a custom report that you can use to report on this metric from Spira.

In Spira we have a nice incident aging graph that you can use to see the count of incidents per aging range. However sometimes customers are looking for more customizable reporting around incident aging data. This article provides some sample custom reports.

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.