Frequently, customers ask for the database model, also called as the entity-relationship (ER) model that shows the relationship between the various entities. While these details can be gathered from the tables exposed, this article shows a minimalistic database model.
Entity SQL uses a little different structure than traditional SQL and sometime, it can be that even if the query is working fine in SQL or T-SQL it may throw an error when creating a custom queries in Spira using ESQL. Here are some of the most known errors that may prevent you from getting a successful result.
A customer once asked how to create a list of all test cases that have electronic signature approval recorded. For example, let us say that you have electronic signature turned on for a specific transition operation in the Test Case. Then, how do we create a list of all the test cases that have electronic signature recorded?
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.
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).
A customer once asked how to create a velocity comparison chart for their Scrum Team to measure planned versus actual velocity across the releases. This article addresses how this chart can be created.