Page Comparison

Conditions control who can perform a transition and the circumstances under which they can perform this transition. If any part of a transition's condition fails, the user will not see the transition link on the 'view issue' page.

You can use JJupin and SIL Power Scripts™ for Jira and SIL™ to define a large set of conditions beside Jira's built-in conditions, by just adding a (k) SIL SIL™ Condition to the transition and publishing the workflow, as described here.

Below are just a few The following common examples explain this feature:

You will need the following JIRA plugin:

Previous status

A workflow condition that allows enables you to disable a particular transition if the current issue has never been in a specific status:

...

number STATUS_OPEN = 1;
string[] status_history = fieldHistory(key, "status");
string previous_status = getElement(status_history, size(status_history)-3);

return previous_status == STATUS_OPEN;

Cascading select comparer

A workflow condition that allows you to disable a particular transition when two cascading selects are equals:

...

//Condition Cascading select comparer

if(length(customfield_10000) == 0 && length(customfield_10001) == 0) { //both cascading select are empty
   return true;
}
if(customfield_10000 == customfield_10001) {
   return true;
}
return false;

Condition based on regular expression

A workflow condition that allows you to disable a particular transition when a custom field value doesn't match to a regular expression:

...

//Condition based on regular expression

return matches(Combo, "accepted(.)(\\\\d+\\\\.?){10}(.)[a-z]+(-)(\\\\d+\\\\.?)"));

Condition based on linked issues

A workflow condition that allows you to disable a particular transition when the current issue has no linked issues:

//Condition on linked issues

if(isNull(getLinkedIssues(key)) || return size(linkedIssues(key))==0) {
   return false;
}> 0;

Condition on non-linked issue

A workflow condition that allows you to disable a particular transition when the current issue has linked issues.It's the reverse condition of the SIL code above:

//Condition on non-linked issue

if(isNull(getLinkedIssues(key)) ||return size(linkedIssues(key)) ==0) {
   return true;
}
return false 0;

Condition based on mathematical expression

...

More details can be found on Math Routinesroutines section.

Condition based on date-time expression

...

More useful date routines can be found in the Date Routines section. 

Compare two parsed texts

A SIL condition which checks if description contains summary:

return description.contains(description, summary);

Except assignee Condition

...

Where customfield_11300 and customfield_11301 are JIRA Jira custom fields of type numeric.

Condition based on equality of time spans

Define 3 intervals and compare them in a condition.

...

A SIL condition which checks if there are less than 3 days and a half remaining before the estimated time will be exceeded:

interval tstRemaining = "3d 4h";

return tstEstimatetstRemaining ==< (tstSpentestimate +- tstRemainingtimeSpent);

In the example above it is used the addition between tstSpent and tstRemainingsubstraction between estimate and timeSpent, but the user can also use the subtraction between tstEstimate and any of the other 2 intervals.addition between two time intervals in SIL.

All sub-tasks must be resolved

The transition won't be shown unless all sub-tasks are resolved. You can also specify a particular resolution that the sub-tasks must be in (in our example Fixed):

string[] subtasks = subtasks(key);
for(string subtask in subtasks) {
    if(%subtask%.status != "Resolved" || %subtask%.resolution != "Fixed") {
       return false;
    }
}

See also

• Validators
• Post Functions