Reporting and Queries

Beside entering an issue and changing its states over the lifecycle, the most common task in project and change management is getting a view on all important issues one is concerned with. For this purpose, the Track+ application currently provides two entry points:

The "My Issues" link provides a list with all issues where the user logged in has been noted as either $ORIGINATOR, $OWNER, or $RESPONSIBLE, and with states in category "open" (e.g. open, implemented, assigned, etc.). This should serve the need of most regular users. The default sort order is by issue number.

For more complex queries, the user can assemble a "filter" via the "Reports" link that restricts the output of the query. While this may not cover every possible need, it should serve most requirements.

Figure 9: Configuring a report

When defining a filter, only one project at a time can be queried. Each selection as shown in Figure 9 restricts issues to those that match the selected criteria. In the example, all issues of project "Caliph++" release "1.5" that are not closed will be reported. If a criteria is not selected it is not being applied. Thus it is the same if one selects all criteria of a certain class or none at all.

The report may be sorted by subsystem, class, priority, severity, and state. The default sort order is as shown in the sort order box.

In this version of the Track+ application the configuration is saved inside the session. Subsequent versions will allow to "can" customized reports so that they can be recalled even across sessions.