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

This section lists out the use cases for the conditions, validators and post-functions of the add-on.

Click on each page for the use cases:

The add-on has conditions that have features which help you to hide/show a transition of a workflow to the users. This section describes some use cases for the conditions.

Related links:

 

Reaching a certain status from several other statuses (through the same transition) and returning to the originating status

You can reach a to certain status from several other statuses, through the same transition and return to the originating status using the Previous status condition. Set this condition on a transition such that its most recent status is the status from which it has transitioned. For more information see; Recipes.

Check for Self review prior to Peer review

In any development life cycle, a deliverable needs a Self Review prior to Peer Review. This can be achieved by using the condition Previous status condition,  on a transition going to the Peer Review status. Set this condition on the transition such that, its previous status is Self Review before transitioning to Peer Review.

Stop user from triggering incompatible transitions

Users can be stopped from triggering two incompatible transitions in a workflow. For example, A user should not be able to Close an issue Resolved by him. Similarly, a user should not be able to Approve a task Developed by him. For such customized scenarios, you can set the Separation of duties condition, on the transition which the user should not be able to trigger, once he has transitioned between two selected statuses. This condition can hence also be used as a security check.

Escalate a bug to the Manager, whenever the bug fix has been rejected.

Whenever a bug fix has been rejected the transition Escalate should be triggered on the issue. However, this transition should not be available for a manual trigger. This can be achieved by placing the condition Hide transition on the Escalate transition and a post-function to trigger it on the rejection of a bug fix. For more information see; Recipes

Create special conditions using Groovy expression

To hide or show a transition under special conditions, you can code a Groovy expression and return a value of true or false. If the result is true then the transition will be available in the workflow actions. Refer the below sample code block:

if (issue.get("issuetype").getName() == "Bug")
{
 return true
}
else
{
return false
}
  • No labels