Page Comparison

...

The ability to add workflow conditions based on the data points available within the Root Cause Analysis plugin provide for an exceptionally flexible method of ensuring that your team consistently performs the required analysis. Conditions are available for all of the data entry fields to allow for the different ways that organizations use JIRA.

A condition to ensure that the Root Cause Issue field is populated can be added to a workflow status transition to prevent the user from moving the issue forward through the workflow. Multiple conditions can be added to ensure that all data points are completed before closing the issue. Alternatively, the Root Cause Analysis plugin can be left as is with no workflow conditions active which will provide no automatic enforcement of performing the analysis.

Workflow Condition Creation Example

1. Log in as a user with the JIRA Administrators global permission.
   
   
2. Click on the JIRA Administration cog Image Added and select the Projects menu item.
   
   
3. Click on the Project link for the project you wish to add workflow conditions to (In this example we will add one to the project Root Cause Test with key RCT).
   
   
4. You will now see the project Administration page.
   
   Image Added
   
   
5. On project Administration page, look for the Workflows section and click on the(edit) icon (beside the RCT: Software Development Workflow linkSoftware Simplified Workflow for Project RCT link).
   Image Removed
   Image Added
   
   

6. You are now presented with the list of Workflow steps and their valid transitions for the projects workflow.

   Image Added

7. For our example lets say we want to ensure that the Root Cause Issue field has been populated before a user could move the issue from In Progress to In Review (essentially blocking the In Review transition between the two states).

8. In the In Progress row, click on the In Review link from within the Transitions column.

   Image Added

    

9. Click on the Conditions tab to display the existing conditions for the transition.

   `Image Added

    

10. Click the Add condition link. You now see the list of available conditions to add to the workflow transition.
    Image RemovedAnalyze the each workflow step and each of the associated transitions to determine which transitions we want the Root Cause Analysis plugin to manage data.
    Image Added
    
    
11. Click the Add button on the next screen to finalize the addition of the workflow condition.
    
    Image Added
    
    
12. You are returned to the list of workflow conditions for the transition. You can see the one you added in the list!
    
    Image Added
    
    
13. Click on the Publish Draft button to make your changes to the workflow active.
    
    Image Added

Now lets try out our newly created workflow condition in action!

1. Create a new JIRA Issue in the project we just added the workflow condition into.
   
   Image Added
   
   

2. Click on the In Progress workflow transition button. Notice that the In Review transition does not appear.
   
   Image Added
   
   

   Note
   If we had added the same condition to the In Progress statuses Done transition, the only available transition at this point would be To Do.

3. Now lets fulfill the workflow condition by entering a Root Cause Issue. Click on the Enter Attributer Data button.
   
   Image Added
   
   
4. Enter a valid JIRA issue key into the Root Cause Issue field. Click the Update button.
   
   Image Added
   
   
5. Notice that the In Review status transition has now appeared since we have satisfied the condition we placed on the transition.
   
   Image Added
   
   

There you have it! Place conditions on any of the Root Cause Analysis plugin fields as you see fit based on your organizations requirements for root cause analysis.