The Root Cause Analysis plugin come bundles with flexible reporting capabilities that allow you to report on root cause attributions in a variety of ways.
Locating the Root Cause Analysis Report
- From the Projects drop-down menu in the JIRA top-level menu bar, select the project you wish to report on (If you plan to change to use a filter instead of a project select any project).
- You should now be on the project Overview page.
- Click on the Reports link on the left hand navigation menu. You will be presented with a page listing the available reports.
- Click on the Root Cause Analysis Report link.
Root Cause Analysis Report Configuration
The configuration screen for the Root Cause Analysis report offers a variety of methods to filter the Root Cause Analysis data within your JIRA instance to generate a meaningful report listing.
- The Project or Custom Filter configuration option, which defaults to the project that you launched the report from, provides the ability to filter the Root Cause Analysis issue attributions made from within a particular project or a custom saved filter. Clicking on the Change Filter or Project... link will allow you to select another project or select a filter from your list of favorite filters, popular filters, or a filter returned by searching all available filters.
- The Root Cause Attributer configuration option can be left blank to have no impact on the filter but if you want to drill down on a particular JIRA user within your Root Cause Analysis report results, you can start typing the JIRA username or the actual name (auto-complete will provide suggestions) and the report will only list Root Cause Analysis entries where the specified user was the Attributer. Alternatively you can click on the
icon to launch the JIRA user picker popup to help select the user to report on.
- The Root Cause Resolver configuration option can be left blank to have no impact on the filter but if you want to drill down on a particular JIRA user within your Root Cause Analysis report results, you can start typing the JIRA username or the actual name (auto-complete will provide suggestions) and the report will only list Root Cause Analysis entries where the specified user was the Resolver. Alternatively you can click on the icon to launch the JIRA user picker popup to help select the user to report on.
- The Root Cause Closer configuration option can be left blank to have no impact on the filter but if you want to drill down on a particular JIRA user within your Root Cause Analysis report results you can start typing the JIRA username or the actual name (auto-complete will provide suggestions) and the report will only list Root Cause Analysis entries where the specified user was the Closer. Alternatively you can click on the icon to launch the JIRA user picker popup to help select the user to report on.
- The Start Date configuration option must be filled in to generate the report. Use the date picker
to select the date you want to start reporting on (the date is inclusive). - The End Date configuration option must be filled in to generate the report. Use the date picker
to select the date you want to stop reporting on (the date is inclusive).
Root Cause Analysis Report Content
Once you have made all of your configuration choices and have clicked the Next button, the report will generate.
If there are no Root Cause Analysis records matching the configuration choices you've selected, you will be shown an empty list with the message "There are no Root Cause Analysis records available for the applied filters..."
Otherwise, you will see a list of Root Cause Analysis entries corresponding to your selected filter configuration.
You can sort the report list by any column (ascending or descending order) by clicking on the column heading of the column you wish to sort by.
You can always change your filter criteria by clicking on the Configure button.
Here is a brief description of the columns included in the Root Cause Analysis report:
| Column Name | Description |
|---|---|
| Root Cause Issue | The issue that was identified as the root cause of the problem being investigated. |
| Attributer Issue | The issue and subsequent investigation that caused the Root Cause Analysis process to be performed. |
| Attributer | The user who identified the Root Cause Issue |
| Attribution Date | The date that the Root Cause Issue was identified (Attributed) |
| Resolver | The user that Resolved the Root Cause Issue. |
| Resolution Date | The date that the Root Cause Issue was resolved. |
| Closer | The user that closed the Root Cause Issue. |
| Closed Date | The date that the Root Cause Issue was closed. |
| Determination | The determination made by the Root Cause Issue Attributer, which can be one of the following:
|
| Review Status | Whether the Root Cause Analysis is complete by all affected parties, either action is still required (one of the summaries hasn't yet been completed) or analysis is complete:
|
