...

This report comes in the form of a line chart report. It provides a snapshot of the team's progress in completing the planned work and achieving goal goals in setted set terms. The report has two lines - guideline and actual line to compare the actual progress to the expected one. On the Y-axis user can see the metric value and on the X-axis user can see the Start and End date.

...

• 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 that the user is hovering over), guideline (show showing the planned amount of completed values till the chosen moment), and unresolved value (amount of left values till the setting due date).

Setting up a report

Report The report has 4 tabs of configurations: Data source, Parameters, Display, Description.

...

Configure and manage the source of data for generating reports.

Project select

...

The “Project“ field is required. It lets the user choose from which project issues will come from.

“Component(s)“ lets the user choose component(s) of a project which let lets the user to get the tickets related to it.

Board select

...

The “Board“ field is required. It lets the user choose the Sprint board.

The “Sprint“ field is required. It lets the user choose Sprint related to choosen chosen Sprint board.

Version select

...

The “Version“ field is required. It lets the user select the tickets related to a certain version.

Saved filter select

...

The “Saved filter“ field is required. It lets the user filter issues by existing filters.

JQL filter

...

The JQL field let lets user filter issues by using JQL requests. Report is using atlassian’s The report uses Atlassian’s JQL component so it has synax syntax checking and auto-complete implemented. When the user finishes inserting the JQL the user needs to validate the JQL using the button underneath the input. Number of issues is clickable. By clicking, the user is redirected to the page with a list of issues in the Jira project.

Parameters

Allow users to tailor the report to their specific needs and preferences.

...

"Duration“ fields are required. There user can choose a start and end date in a datepicker. Out of this will be defined duration. Datepicker also contains a dateswapper, allowing the user to quickly switch months. Minimum The minimum timeframe can be 2 days, maximum - 3 months.

Some specifics about duration in case of choosing Sprint in DataSource:

• If there is a start date setted set for Sprint and a duration (except for custom)  the end day will be calculated based on them.

• If a custom duration is selected, the start date and end date will be taken only if they have been specified in Sprint.

• In case if dates haven`t been specified, the user has to select them in the Duration fields.

Some specifics about duration in case of choosing Version in DataSource:

• If the Version has a start and end date it will be setted set in a 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 have 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“ 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” toggle let lets user 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“ lets the user select the time unit to customize the displayed data on the report. By default, it setted is set as days.

Some specifics for choosing the period:

• If the user select selects days, it will be shown as week day weekday and date. An example: Fri, Jan 12.

• If the user select 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.

• Weeks period A week can be chosen only for duration more than 21 days and for a number of days that is a multiple of 7.

The “Show label“ toggle enables/disables the dots that indicate a chosen period value.

Description

Serves It serves as a space where users can provide context, explanations, and additional information about the report.

...

Description let lets the user add any additional information of less than 500 characters about the created report.
The description will be presented directly on the report card (in case of its presence).

...