🖇️ Navigation | |
|---|---|
|
...
This report gives information about the project status. Whether it is On track, Off track, or At risk.
For Story points and Issue count:
If we have less than 85 - 89% issues completed - At risk.
If 90 - 100% of issues completed - On track.
If we have less than 85% - Off track.
For Work ratio:
Off Track: If the work ratio is above a certain threshold, it indicates that the project is falling behind schedule. You might set a threshold like 120%, meaning if the work ratio exceeds 120%, the project is considered off track.
On Track: If the work ratio is within an acceptable range, the project is on track. This range could be, for example, between 89% and 120%.
At Risk: If the work ratio is below a certain threshold, it indicates that the project may be at risk of not meeting its targets. This threshold could be, for instance, 89%.
...
While hovering the line tooltip appears. It shows the selected date (one the user is hovering over), guideline (showing the planned amount of completed values till the chosen moment), and unresolved value (amount of left values till the setting due date).
Labels on the line can be added and removed. While they are added the user can see the number of tasks created or resolved at a certain moment.
...
Configure and manage the source of data for generating reports.
Project select
...
The “Project“ Project field is required. It lets the user choose from which project issues will come from.
“ComponentComponent(s)“ lets the user choose component(s) of a project which lets the user get the tickets related to it.
Board select
...
The “Board“ Board field is required. It lets the user choose the Sprint board.
The “Sprint“ Sprint field is required. It lets the user choose Sprint related to chosen Sprint board.
Version select
...
The “Version“ Version field is required. It lets the user select the tickets related to a certain version.
Saved filter select
...
The “Saved filter“ Saved filter field is required. It lets the user filter issues by existing filters.
...
Allow users to tailor the report to their specific needs and preferences.
...
"Duration“ Duration fields are required. There user can choose a start and end date in a datepicker. Out of this will be defined a timeframe. The minimum timeframe can be 2 days, maximum - 3 months.
...
If the Version has a start and end date it will be set in Duration fields.
If the Version has a start date and the end date is absent, in duration field will be shown the start date. In that case, user has to specify the end date.
If the Version has an end date and the start date is absent, in duration field will be shown the end date. In that case, user have to specify the start date.
The “Metric“ Metric field is required. It lets the user choose the metric of the key performance indicator by which the report will be calculated. For example: Issue count, Story points, and Work ratio.
The “Include weekends” Include weekends toggle provides the user the possibility to include or exclude weekends while building a report.
...
Manage the visual appearance and presentation of the report, including the visibility of specific elements and the formatting of data.
...
“Period“ Period lets the user select the time unit to customize the displayed data on the report. By default, it is set as days.
...
If the user selects days, it will be shown as weekday and date. An example: Fri, Jan 12.
If the user selects weeks, it will be shown as the first day of the week - the last day of the week. An example: Jan 1 - Jan 7.
The “Show label“ Show label toggle enables/disables the dots that indicate a chosen period value.
...