Our new Appfire Documentation Space is now live!

Take a look here! If you have any questions please email support@appfire.com

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 70 Next »

A workflow condition that enforces separation of duties (for SAS-70 compliance), i.e. it makes sure that the same user cannot trigger two incompatible transitions on the same issue.

 Want to add this condition? Click here to see how..
To add Separation of Duties Condition to a transition:
  1. Click Edit for the workflow that has the transition you wish to configure the condition on.
  2. In the Workflow Designer, select the transition.
  3. Click on Conditions in the properties panel.
  4. Click on Add condition.
  5. Select Separation of Duties Condition from the list of conditions.
  6. Click on Add to configure the condition on the transition.
  7. Select the originating status of the transition from the From Status drop-down.
  8. Select the destination status of the transition from the To Status drop-down.
  9. Click on Add to add the condition to the transition. 

Specifying the incompatible transition

JIRA does not keep a track of the actual transitions (or workflow actions) but only of the changes in the status of an issue. So, it is impossible to distinguish between two transitions that share the same source and destination statuses. Therefore, this condition requires that you specify transitions in the form of a destination status and a source status (or Any for all transitions leading to the destination status).

 

When you set this condition on a transition, the add-on checks whether the current user has triggered any transitions between the selected From Status and the To Status. If a transition has been triggered between the two selected statuses by the current user, then the transition on which the condition is configured will be hidden from the user.

In short, the selected transition will be available to the user, as long as the user never triggered any transition between the two selected statuses.

Refer Use cases for conditions page for use cases for this condition.

 

  • No labels