Release Efficiency Dashboard

Problem to solve

Release managers are often asked about historical performance of releases. Also, as a value we want to improve the efficiency of our user's releases by giving them insight in to how their releases are performing

Intended users

• Rachel (Release Manager)
• Delaney (Development Team Lead)
• Sasha (Software Developer)
• Devon (DevOps Engineer)

Further details

• Use case 1: a release manager working across many teams may need to report out how frequently a particular environment is being released to and of those releases,
  • how many were successful or failed
  • % of success/fail

An example from XL Release, a competitor, is a template below:

• Use case 2: a developer lead may want to see how frequently their team is pushing code to production
  • % of successful/fail releases by group and environment
  • Number of successful/fail releases by group and environment

Proposal

• Create a dashboard in the release page that allows you to filter on project or environment or group that displays the number and % of successful and failed releases for that project in the last 4 weeks by default
• The data in the dashboard must be exportable by project, environment or group

Permissions and Security

• The dashboard only displays aggregated numbers for the releases
• The export for the dashboard can contain the release information: release name, description, number of issues, milestone but not an actual export of the issues within the release
• The export must confirm that the user has access to the group, project, and release summary before data is surfaced
• The export will be filtered on the data of which the authenticated user has access - for example, if the user is a contributor and cannot see confidential issues in a project when logged in, the release issue count will reflect only public issues

Documentation

• Link to be provided when documentation is created

Testing

• Confirm access permissions to the data based on authenticated user
• If user is unauthenticated the dashboard will only render public releases
• If user is authenticated and can see confidential issues, those will be included in the issue counts of the exports

What does success look like, and how can we measure that?

• Export usage should increase MoM and we should see an increases in release usage as they can manage their releases more

What is the type of buyer?

• Premium+

Links / references

• Release XL