Issue status (Delivery)

Target Audience

This report is designed for Engineering leads, Scrum masters who need to assess the overall status of tickets (e.g. Jira stories/tasks) executed by the team. The insights provided in this report can be leveraged effectively to run rituals e.g. daily stand-ups.

Report Overview

The Issue status report serves to:

1. Highlight Flags: Display flags associated directly with the issues (and the Feature branches/PRs associated with the issues).

2. Indicate Delivery Status: Indicate the delivery progress of the feature.

3. Indicate Released Status: Indicate the status of release in production or the underlying PR reaching the configured production branch (in the configurations associated with the code version control system).

4. Perform Planned Vs. Actual analysis: With the assumption that the team does effort estimations, this indicates the actual effort spent on an issue (in comparison to the planned effort).

5. Showcase Subtasks: Showcases all the subtasks associated with the issue (as planned in the project management tool)

Issue Health Analysis

The report computes the health of an issue using:

• Flags associated directly with the issue (OR)
• Flags associated with sub-tasks of the issue (OR)
• Flags associated with Code branches/PRs of the issue/sub-tasks.

Note: Rules for computing the health can be customized using the report configurator.

Optional Deep Dives

Users can explore a variety of data points across the following categories:

1. Core Issue Data: Metrics shown in the Overview section, extracted from project management tools (e.g., Jira). These provide insights into execution of the issue and potential impediments for closure.

2. Deployment Data: Metrics in the Deployment Overview section (available when a CI/CD tool is integrated) offer insights on:

   • Deployment frequency.
   • Average deployments across environments.
   • The intent to not just build but also deploy the the functionality to end-users.

3. Cycle Time Data: Metrics in the Cycle Time Overview section are derived from project management tools (e.g., Jira) and version control systems (e.g., GitHub). These metrics provide a holistic view of completion of the issue.

4. Pull Request/Merge Request Data: Metrics in the PR Breakdown section highlight progress and code quality associated with an issue.

Data sources

The report integrates data from:

1. Project Management Tools: e.g., Jira.
2. Version Control Systems: e.g., GitHub.
3. CI/CD Tools: e.g., Jenkins.

Recommendation: Connect your project management tool and version control system to unlock the full potential of this report.