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.
You may need to create a report of Tasks with their folders. From Spira v8.3 it is now possible to display the name of the folder, just like it can be done for Test Cases and Test Sets
To get a table that summarizes the test run count by status / by build, this article explains how to accomplish this.
You may want to see what product membership for a product was like historically - what users in what role were able to access the product at a specific point in time.
Starting from Spira 7.13 it is possible to track product membership changes and use custom reporting to review this historical data.
This article explains how to get the most recent comment and add it as a column for an artifact summary report (if it is not already displayed).
This article describes how to retrieve artifact's associations due to the dependency type that become challenging.
A customer asked us the following question: "I run an automated test suite consisting of the same 250 tests every night.I'd like to be able to run a report in the morning that shows me the tests that failed, but had passed the previous night.How can I accomplish this using the reporting mechanism ??"
You’ve probably encountered cases where it looks like you need another SELECT statement inside your main statement.Is it possible to use nested SELECTs in ESQL? Yes, it’s possible!In this article, we’ll explain the nested query (SELECT) and how to use it efficiently.
You may want to extract all the artifacts that have a specific person is assigned across all products, to see their current work. This article provides an example of such a report.
If you need to connect Database object to PostgreSQL database follow these simple steps.