Warning |
---|
Looking for the documentation on the newest versions of SIL Engine and the Simple Issue Language for Jira 8 for Server/Data Center? Click here ! |
Info | ||
---|---|---|
| ||
|
...
Tip | ||
---|---|---|
| ||
Starting with katl-commons SIL Engine™ 2.5.3, the "skipStateCheck" parameter was added that allows to force the target transition even if the issue is currently inside another transition and has been modified. |
...
Tip |
---|
On the cloud version, you can only use: autotransition(transitiontransitionId, issueKey) |
Description
Excerpt |
---|
Executes a transition and moves to the specified step. It will execute the transition only if the transition is valid for the current status of the issue. |
...
Info | ||
---|---|---|
| ||
To use the routine on the Create Issue transition, it is very important that you place the SIL post function after the "Creates the issue originally" post function but before "Fire a Issue Created event that can be processed by the listeners.". Positioning the SIL SIL™ post function otherwise will de-synchronize the issue from the workflow. That will set an invalid status for the workflow step it is in. |
...
Parameter name | Type | Required | Description | ||
---|---|---|---|---|---|
transition | string | Yes | Id or the name of the transition that will be executed.
| ||
issuekey | string | Yes | Key of the issue the transition will be executed for. | ||
skipStateCheck | boolean | No | If set to "true", will force the target transition even if the issue is currently inside another transition and has been modified. | ||
skipConditions | boolean | No | If set to true, will not check conditions on the target transition | ||
skipValidators | boolean | No | If set to true, will not check validators on the target transition |
...