In order to provide the level of valuable feedback to users that worked on issues attributed as the Root Cause Issue of an Attributor Issue, the Root Cause Analysis plugin needs to be able to get access to certain information that is only available at the point of certain during workflow status transitions. The workflow status transitions that are applicable to the plugin will differ from workflow to workflow based on how your organization uses JIRA.
There are two workflow post functions that come bundled with the Root Cause Analysis plugin:
- Root Cause Analysis Resolver Saver - Used to save the JIRA user id as well as the date/time of a particular workflow status transition where the transition is causing an issue to be change complete.
- Root Cause Analysis Closer Saver - Used to save the JIRA user id as well as the date/time of a particular workflow status transition where the transition is causing an issue to be verification complete.
The data obtained from the placement of these two workflow post functions will appear on the Root Cause Analysis panel within each issue that has attributed a Root Cause Issue.
We feel that allowing you to specify which status transitions will map to the Resolver and Closer fields in the Root Cause Analysis plugin provides the ultimate in flexibility from the simplest to the most complex workflow processes.
As a working example, lets go through the Root Cause Analysis workflow configuration process for JIRA's Software Development project type and its associated Software Development workflow...
...