...

• 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 the percentage of completed issues/story points is in the range of 85 - 89% issues completed - At risk.

  • If 90 - 100% of issues/story points completed - On track.

  • If we have the percentage is equal to or less than 85% 84% - Off track.

• For Work ratioRemaining estimate:

  • 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.remaining estimate completion is equal to or less than 84%.

  • 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%remaining estimate completion is 90% - 100%.

  • 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%.

...

• • remaining estimate completion is in the range of 85-89%.

...

• In the top-left corner of the chart, selected data source is displayed, along with a clickable link that navigates to Jira.

• 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 set due date).

• Labels on the line shows unresolved value for each day and the difference with the guideline value. Labels can be added and removed. While they are added the user can see the number of tasks created or resolved at a certain moment.

...

• The report is built considering all issue types.

Setting up a report

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

...

The Project field is required. It lets the user choose from which project issues will come from. By default, it is set as a project where the app was opened.

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

...

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

Version select

...

The Project field lets the user choose from which project versions will come from. By default, it is set as a project where the app was opened.

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.

...

The JQL field lets user filter issues by using JQL requests. The report uses Atlassian’s JQL component so it has syntax checking and auto-complete implemented. When the user finishes inserting the JQL the user needs to can 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.

...

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

...

Duration fields are field is required. There user can choose a start and end date in a datepicker. Out of this will be defined a timeframe for the report. The minimum timeframe can be 2 days, maximum - 3 months60 days.

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

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

• 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 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 DataSourceData Source:

• 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 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 Remaining estimate. The default value for this field is Issue count.

The 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 lets the user select the time unit to customize the displayed data on the report. By default, it is set as days.

Some specifics for choosing the period:

• 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 toggle enables/disables the dots that indicate a chosen period value.

...