Contents
| Table of Contents | ||||
|---|---|---|---|---|
|
One of the best features in Power Scripts™ is customizing workflows. Using the power of SIL, you can add conditions, validators, and post functions on any transition from your workflow.
...
After you install Power Scripts™ for Jira, go to the Administration > Workflows page and create a workflow, associated with a project.
...
An important consequence of the above model is that conditions and validators should not have side-effects. In fact, Power Scripts™ for Jira is discarding modifications of the issues, allowing them to occur in the post function only but it cannot discard modifications made on another database, for instance, applied using the sql routine (see sql() routine for details).
...
| Info | ||
|---|---|---|
| ||
Starting with Power Scripts™ for Jira 4.0, your SIL program will be saved either on the disk in the folder specified in the configuration or in the database. The filename is obtained by removing any invalid characters from the program name you entered and appending a number to help you browse through different versions of the same file. |
...
Returns codes are different for validators, conditions and post functions.
For validators
| Code Block |
|---|
return false, "assignee", "We have failed, assignee is not ok"; |
...
For example, you can check whether certain fields were filled out during a workflow transition. To do that, use the hasInput routine.
For conditions
| Code Block |
|---|
return false; //to signal that condition is not fullfilled. |
Just tell Jira this condition is not fullfiled.
For post functions
| Code Block |
|---|
return; |
return ends the program, any values are ignored.
...