Capture new JIRA workflow event metrics to enhance your company or team performance objectives, and create new company KPIs using the collected data.
In the context of a Support team these might look as follows:
- Support Iterations – the number of times an issue is returned to support. It might be used for KPIs, e.g. Decrease back-and-forth in workflow.
- Supported by – the JIRA user that investigated the issue. In many cases it might differ from the assignee. Identify more accurately the key contributors within the team with KPIs, e.g. First Contact Resolution (FCR)
- Support Started – the start date of support that might be used to track KPIs, e.g. First Response Time (FRT).
In the context of Quality Assurance these might be:
- Test Iterations : Number of times an issue was in testing. Set metrics that decrease the repeating cycles. Combined with “Resolution” (e.g. “Duplicate”, “Cannot reproduce”, “Not a defect”), this will help to improve team punctuality by setting KPIs, e.g. Punctuality of reported defects.
- Tested by : The user that resolved / transitioned an issue from “Testing” status to “Done” (or “Resolved”, or “Closed”). This will allow setting individual goals to a QA or a Development team member with KPIs such as Decrease time spent in rework.
- Testing Start: The time when an issue was moved to status “Testing”. Capturing such event date enables creation of derive metrics based on Avg. time between events, e.g. Cycle Time KPI.
Adapt the same technique to track similar information, e.g., Review Iterations, Reviewed By, Reopen Iterations, Reopened By, or whatever fits most to your workflow.
Step 1: Add JIRA Custom Fields
Add JIRA custom fields that will store the workflow events info that you would like to track and use within your KPIs.
Check the following JIRA configuration of new custom fields: Support Iterations, Supported by and Support Started date.
Step 2: Capture new JIRA workflow events
Locate the JIRA workflow(s) that serves the issue type(s) in which you are interested to set metrics. Identify the transition step(s) within the workflow, and set post functions. These post functions will store data from the issue context within the Custom Fields. This will allow future analyses and setting new company goals as part of your OKR process.
Please check the following recording with exact JIRA configuration steps.
Step 3: Create new KPIs using the collected data.
Check the following popular KPI examples with their configurations in JIRA.