- Custom Graphical Reports (obsolete, supported for on-premise only)
- Typical setups of views and dashboards
- Custom Formulas and Language for Advanced Report Customization
- 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
- Graphical Reports: Data Filters and Chart Definitions
This article is obsolete for On-demand accounts. Please see our guide section on how to create Visual Reports.
There are many ways to use Custom Reports and Left menu folders effectively, here are just a few ideas:
- Area focus: Create a QA folder and gather all quality related reports there
- Team focus: Create a folder related to some team (for example, Alaska) and create several reports that show progress, quality, time tracking, etc information for Alaska team only.
- Project/Program focus: Create a folder related to a specific and create charts like average Cycle Time, New bugs trend, closed bugs trend, etc. for this project.
Team Focus Case
Let’s review a real case for Team focused folder. We have team Alaska and here is its folder in Left menu:
It has one dashboard, several reports and some views. Let’s review these reports and see what we can discover.
Cycle Time by Month
This report answers a question “Do we release User Stories and fix Bugs faster than before?” In this case the team has a goal to release stories in 10 days or less. We see that in July and September the team achieved this goal, but now cycle time degrades.
Bugs and Stories Closing trend
This chart answers questions “Do we implement more User Stories every month?” and “Do we fix more Bugs?” We see that team performance had been increasing steadily in spring till August, but went down slightly in fall.
Shows how much effort the team delivers every week.
Effort vs. Cycle Time
Shows correlation between the User Story effort and the cycle time. You spot User Stories that were estimated 1-3 points, but it took 3-5 weeks to release them. You can click on every User Story and dig into more details.
Stories Sizes trend
On a retrospective meeting the team agreed to split User Stories better. However, this report shows, that this is not happening. Average effort of completed User Stories increases.
The latest problematic User Stories
Finally, we wonder what User Stories had the most Bugs recentely? This report clearly shows that 3 User Stories had 9 Bugs, while all the other User Stories we completed in the last 2 months had less:
Still have a question?
We're here to help! Just contact our friendly support team
Get Started for free
Manage complex work, projects and products with Targetprocess
We’ve sent you a confirmation e-mail — please, go check it.
With our product specialist Ksenia