- Custom Graphical Reports (obsolete, supported for on-premise only)
- Use Cases
- Done items count per user (obsolete)
- Count of assigned items per user (obsolete)
- Estimated effort vs time spent per user (obsolete)
- Creating Basic Custom Graphical Reports from Templates
- Reference for Advanced Charts Creation
- Custom Formulas and Language for Advanced Report Customization
Requires Targetprocess 3.6.0+
This article is obsolete for On-demand accounts. Please see our guide section on how to create Visual Reports.
Let’s dig into a more advanced setup. Click the Setup tab:
In Targetprocess’ graphical reporting tool, report setup has two main areas: Data source selection on the left and Chart definition on the right.
This is the same Cycle Time trend chart we have seen before. Here’s what’s going on.
Here we select data for the report. It is similar to View setup. For information about User Stories, click the User Story button. It is possible to select several Entities at once (these Entities should have common properties). For example, if we want to see cycle time for User Stories and Bugs, we select them both.
Then, filter selected Entities to see cycle time for the last 6 months with include only completed User Stories and Bugs. To create a filter:
?EntityState.IsFinal is true and EndDate >= Today - 182(days)
Read more about filters and how to use them.
The system remembers the combination of projects and teams for this report. Use "Set default project and teams" to select and save required projects and teams.
In this section, we use project graphical report software to map data variables to visual dimensions (X, Y axis, color and size). Simply tell the report what you want to see on the X-axis, Y-axis, etc. First, we’ll check the Cycle Time trend report that was previously presented then move to a more general discussion.
On the X-axis we want to see dates by weeks. We don’t want abstract dates so we use properties that exist in User Story and Bug Entities. These Entities have EndDate property, it indicates when Entities were moved to a Done state. Then, we group cycle time by weeks with an aggregation for EndDate
The Y-axis is more complicated. We want to see cycle time for several projects. It means we need to group cycle time by project. In this case, we have to map Y twice: the first mapping defines this grouping by project, and the second defines what we really want to see inside (in our case it is an average cycle time).
Color is used to draw two lines: one is for User Stories in blue and the other is for Bugs in red. All Entities in Targetprocess have the EntityType property. Here it is in action:
Finally, we select a chart type. This is a simple line chart.
One final pro-tip… you need to define chart definition fields. There is no autocompletion or hints in the tool today. earn what properties you can use with this reference.
With graphical reporting tools in Targetprocess, you can immediately get insights into a project’s progress with a quick glance. See which project areas require more time and effort, spot bottlenecks ahead of time and improve risk management with our project graphical reporting software.
a sales representative
Get a live
Let one of our product specialists create your account
and shape Targetprocess for your company needs.