We recently helped a client implement this model in Jira with the help of Abacus—the Jira Calculator. Here’s how it worked:
The first step in the process was to create 16 Custom Fields in Jira corresponding to the 16 Risk Factors used in OWASP methodology. Risk Factors are divided into subgroups, including:
For our client’s “Risk” Issue Type in Jira, we configured 4 tabs on the Create Issue Screen to correspond to each of the four subgroups (Threat Agent, Vulnerability, Threat Impact, and Business Impact). On each of these tabs, the related factors were listed with dropdown menus ranging from 0 to 9 for assigning the relative risk rating of each factor.
A fifth tab was created to display the average Risk Ratings (0 to 9) and the corresponding Impact Levels (Low, Medium, High) for these subgroups.
In order to calculate average Risk Ratings for the subgroups and assign the corresponding Impact Levels, we used Abacus, an app specifically designed for creating calculations in Jira.
Using Abacus, we applied the “Average” function to create formulas for the following subgroups:
Next, an Execution Plan named “Severity” was created to determine when and how the formulas would run. The Issue Events “Issue Created” and “Issue Updated” were selected to trigger the formulas. Now, whenever an issue is created or updated, the formulas will run automatically. Finally, Execution Groups were used to Edit Issue Fields with the Impact Levels for each of the average Risk Ratings. Three Group tabs were created for the following factor subgroups: Overall Likelihood (displayed below), Overall Technical Impact, and Overall Business Impact. Using IF and ELSE IF statements using JQL, we were able to edit the fields with the corresponding Impact Level.
Using Abacus and Jira together helped our client monitor the Likelihood, Technical Impact, and Business Impact of issues facing their company.
Abacus can be used to create a wide variety of other simple and complex numerical, date, and duration formulas. Is it time to solve your Jira?
Users of Abacus already know the value of automating calculations within Jira to save time and energy. A well-configured formula can save a team hours of work, allowing them to focus on delivering value to their stakeholders while Abacus calculat...
Teams prioritizing their backlog using Weighted Shortest Job First (WSJF) know the importance of minimizing costly delays. They also know it can be a difficult process to implement in Jira. In this post, we’ll show how pairing Abacus with Jira can...
Estimating work is one of the hardest – and most important - operations for an Agile team to get right. While story points can be a trustworthy companion to your team, they're not a one-size-fits-all solution. What if your team wants the flexibili...