Release readiness report
The Release readiness report details criteria based on internal standards and compliance requirements.
- Are release preparations final and is the version meeting all quality criteria?
- Did the reviewers submit the required approvals?
- Is the version thoroughly and properly tested against the quality criteria?
- Do specific issues exist for this version now that require additional attention?
- Click
Insights, and then select Reports. - Select the Release readiness field under the
Templates heading on the left side of the page.Note: When the Release readiness field is selected, a vertical blue bar is displayed on the left side of the field to indicate it as the report to run.
- Click the Run report button to display the RUN REPORT window.
- In the Pipeline / value stream drop-down, select the required value stream and pipeline from the list.
- Optional: In the Stage containing release candidates (optional) field, enter the pipeline environment containing the release candidates.
- Optional: In the Targeted release stage (optional) field, enter the
environment.Note: To set the report inputs as default, click the Set as Default button.
- Click the Confirm button to run the report.
- If the report ran successfully, in the Status field of the table
below the Run report button, a green circle and
Complete is displayed. Note: If a red circle and Failed is displayed, run the report again.
- After the report runs successfully, in the line item for the report in the table, click Results to view the Release readiness report.

- Report header
- Release summary
- Release content
- Release quality & security
- Release process
| Main section | Subdivision |
|---|---|
| Report header | Value stream name, Release name with Scheduled date, Application name with CANDIDATE and CURRENT VERSION details, Readiness score, Time in stage, Deployment success rate |
| Release summary | Release summary |
| Release content | Candidate version, Changes introduced since version (number), Contributors, and Individual Measures. |
| Release quality & security | Approvals, Current version quality & security metrics, Current application quality & security metrics, Pipeline gates |
| Release process | Release activites, Value stream - highest priority items opened |
Report header
Under the Application name in the report header, the CANDIDATE and CURRENT VERSION details including environment, version, and date are displayed for each. These two versions are compared with one another with the results listed in the report sections contained in the table above. The Readiness score, Time in stage, and Deployment success rate details are also displayed in the report header.
Readiness score
icon in the bottom right hand corner of the section. The
Readiness score details are listed in tabular form with the fields
detailed and shown in the following table and figure respectively.| Field | Description |
|---|---|
| Status | Indicates the state of the specific criteria as success or fail with the green or red symbols respectively. |
| Criteria | Specific area of focus for this release candidate. |
| Target | Based on the criteria, what is the optimal value for success? |
| Actual | Based on the criteria, what actual value was achieved? |
| Score | The percentage of success between the Score and Actual values. |
Release summary
Release content
The Candidate version section identifies details for the specific build including names, issues, PR and commits. The Changes introduced since version (number) section lists the items that are added to the CURRENT VERSION to represent the CANDIDATE version including issues, PR and commits. The names and number of owners providing changes for the aforementioned items in the new version are listed in the Contributors section. Links are provided in each of the aforementioned sections to view information for specific items. You can also see the individual measures for the contributors of the release. See the Individual Measures section for more details.
Individual Measures
The Individual Metrics section, available in the Release Readiness Report, provides detailed insights into the performance and involvement of each contributor in the release. This data is essential for engineering managers, product owners, and team leads to assess individual efficiency, promote accountability, and drive continuous improvement.
For every contributor who has participated in the release, the following metrics are displayed:
-
Number of Issues Completed
Tracks the number of tasks (stories, bugs, or technical items) a contributor has completed. This metric helps evaluate task throughput and individual contribution levels.
-
Total Story Points Completed
Measures the total effort delivered by a contributor based on the story points assigned to completed work items. This metric supports capacity planning and performance evaluation.
-
Number of Pull Requests Created
Indicates the frequency at which a contributor submits the code changes for review. This metric provides insight into coding activity and collaboration with peers.
-
Total Number of Commits
Shows the number of code commits made by a contributor, reflecting consistency, development cadence, and active involvement in coding tasks.
-
Dev Cycle Time
Measures the duration a contributor takes to complete a work item, calculated based on the specific stages configured for Dev Cycle Time within your value stream. This metric is useful for identifying delays, inefficiencies, or areas needing support or process improvement.
-
Dev Cycle Time per Story Point
Normalizes Dev Cycle Time by story point size, allowing teams to evaluate individual efficiency relative to task complexity. This metric helps in identifying high-performing contributors or highlighting potential mismatches between estimated and actual effort.
Individual Measures are displayed in a tabular format within the Release Readiness
Report, as shown in the following example, offering a clear overview of the contributions
and performance metrics of each contributor for the release.
Release quality & security
Release activities
In this section, you can view scheduled or releases in progress and any prerelease activities necessary prior to moving into the production environment. Links to specific release activities are provided in this section.
Value stream - highest priority items opened
This section monitors specific issues in the value stream for the candidate version that require attention and resolve prior to release. Links to specific work items are provided in this section.