Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

In order to provide the level of 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 workflow status transitions. The workflow status transitions that are applicable to the plugin will differ from workflow to workflow.

 

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...

  1. Start by clicking the Projects drop-down and select Create Project
  2. Select the Software Development project type and click Next
  3. Click Select on the next screen and enter a Project Name and Key. I'll use Root Cause test with a key RCT.
  4. Click Submit to finish project creation.
  5. You will now be on the project Overview page. Click on the Administration link near the top of the page.
  6. On the resulting project Administration page, look for the Workflows section and click on the(edit) icon beside the RCT: Software Development Workflow link.
  7. You are now presented with the list of Workflow steps and their valid transitions for the projects workflow.

  8. Analyze the each workflow step and each of the associated transitions to determine which transitions we want the Root Cause Analysis plugin to manage data.

    Step NameTransitionTrack Data for ResolverTrack Data for CloserReasoning
    To DoStart Progress(error)(error)When in the To Do status and the Start Progress transition is triggered, the user is just starting work so we don't care to track anything from this specific transition for Root Cause Analysis plugin purposes.
    ''Done(tick)(tick)When in the To Do status and the Done transition is triggered, the user performing the action is both marking the issue as change complete and verification complete. The Root Cause Analysis plugin will want to gather information from this status transition for both the Resolver and the Closer.
    ''Start Review(tick)(error)When in the To Do status and the Start Review transition is triggered, the user performing the action is marking the issue as change complete. The Root Cause Analysis plugin will want to gather information from this status transition for just the Resolver at this time.
    In ProgressStart Review(tick)(error)When in the In Progress status and the Start Review transition is triggered, the user performing the action is marking the issue as change complete. The Root Cause Analysis plugin will want to gather information from this status transition for just the Resolver at this time.
    ''Done(tick)(tick)When in the In Progress status and the Done transition is triggered, the user performing the action is both marking the issue as change complete and verification complete. The Root Cause Analysis plugin will want to gather information from this status transition for both the Resolver and the Closer.
    ''To Do(error)(error)When in the In Progress status and the To Do transition is triggered, the user is moving the issue back in the workflow so we don't care to track anything from this specific transition for Root Cause Analysis plugin purposes.
    DoneReopen(error)(error)When in the Done status and the Reopen transition is triggered, the user is moving the issue back in the workflow so we don't care to track anything from this specific transition for Root Cause Analysis plugin purposes.
    ''Reopen and start progress(error)(error)When in the Done status and theReopen and start progress transition is triggered, the user is moving the issue back in the workflow so we don't care to ever track anything from this specific transition for Root Cause Analysis plugin purposes.
    ''Reopen and start review(error)(error)When in the Done status and the Reopen and start review transition is triggered, the user is moving the issue back in the workflow so we don't care to ever track anything from this specific transition for Root Cause Analysis plugin purposes.
    In ReviewDone(error)(tick)When in the In Review status and the Done transition is triggered, the user performing the action is marking the issue as verification complete. The Root Cause Analysis plugin will want to gather information from this status transition for just the Closer.
    ''Restart Progress(error)(error)When in the In Review status and the Restart Progress transition is triggered, the user is just starting work so we don't care to ever track anything from this specific transition for Root Cause Analysis plugin purposes.
    ''To Do(error)(error)When in the In Review status and the To Do transition is triggered, the user is moving the issue back in the workflow so we don't care to track anything from this specific transition for Root Cause Analysis plugin purposes.
  9. Based on the analysis above, we will need to add workflow post functions to five transitions. Moving down the list from the top, lets add our post functions to the Done transition within the To Do step.

  10. Click on the Done link in the To Do row under the Transitions column.
  11. Click on the Post Functions tab. You now see the list of existing post functions for the transition.
  12. Click the Add post function link. You are presented with a list of available workflow post functions.
  13. Select Root Cause Analysis Resolver Saver and click Add

 

 

 

  • No labels