Manage risk in Jira using an app built with Connect.
Teams already track their work in Jira. They include information such as time estimates, the stage in the workflow, and priorities. Jira makes these easy to record with custom places to include the information. However, there's nowhere dedicated to tracking risk or mitigation techniques. Jira Risk gives users a dedicated place to record risk and incorporate it into their workflow.
Our target uses are release managers and people working in DevOps. Release managers can use Jira Risk to review risks, see which issues they should investigate, and check how risky each release is. When an incident happens, someone working in DevOps can use the risk details to identify possible explanations quickly. They can then use the risk details, and people involved to review and improve their development process.
Other apps approach tracking risk with a set matrix, but we want to give teams the flexibility to align on their own definitions of what constitutes a risky change. We also introduce the idea of reviewing risk. A risk review enables people to balance high-risk changes with mitigation techniques.
What it does
- Issue glance: Enter how risky the change is and provide details to explain the risk and the mitigation tactics.
- Project page: See the aggregate risk details, filter by version, and review the risks. If the risk details are acceptable, you can approve the risk.
- Version summary: View a high-level summary of the risk going into a version from the version page. Jump between the summary and full details with the navigation provided.
- Validator: Enforce the use of Jira Risk by adding a validator to the workflow that prevents an issue from transitioning without the risk level set.
- Project-level configuration: The app can be disabled at the project level for teams that don't need to use it.
How we built it
We used Atlassian Connect Express (ACE) to get started quickly. We built the frontend with React, TypeScript, and Atlaskit. The app is hosted on Heroku.
Challenges we ran into
- We used an extension point on the version page that we discovered with the suggested tooling. However, we cannot know which version the page is for from our app. We asked a question about this at the start of Codegeist, but it has not been resolved. See JSWCLOUD-19011.
- No ACE template uses React, so we had to create our own before we could start.
Accomplishments that we're proud of
- The app is ready to scale to large projects with a lot of issues.
- We were able to create a Forge app that is compatible with this Connect app.
What we learned
With mainly back end development experience, Codegeist was a great chance to learn some popular front end technologies and experiment with some parts of Atlassian products that were new to me.
- Bitbucket pipelines
- Entity properties, JQL, and the Jira REST API
What's next for Jira Risk
- List the Connect app on the Atlassian Marketplace.
- Provide documentation to help users get started.
- Monitor usage and feedback to help prioritize our backlog.
- Investigate migrating the Connect app to AWS Lambda.
- Continue developing the Forge app as the platform matures.