...
applyColStyleToCell | true |
---|---|
heading | 0 |
columnTypes | s,s,s,s |
multiple | false |
columnAttributes | style="background:#e5e7ea;font-weight:bold,,style="background:#e5e7ea;font-weight:bold, |
enableSorting | false |
...
Info | ||
---|---|---|
| ||
|
Syntax
autotransition(transition, issueKey)
Tip | ||
---|---|---|
| ||
Starting with 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. |
autotransition(transition, issueKey, skipStateCheck)
autotransition(transition, issueKey, skipStateCheck, skipConditions, skipValidators)
...
Package
...
Alias
...
autotransition(transition, issueKey),autotransition(transition, issueKey, skipStateCheck)
...
Pkg Usage
Description
Excerpt | ||
---|---|---|
| ||
Tip | ||
On the cloud version, you can only use: autotransition(transitionId, 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. |
If the skipStateCheck parameter is set to true, the routine will force the target transition even if the issue is currently inside another transition and has been modified.
...
Info | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Table plus | |||||||||||
| |||||||||||
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™ post function otherwise will de-synchronize the issue from the workflow. That will set an invalid status for the workflow step it is in. |
Parameters
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 |
Return
...
type
Boolean boolean (true/false)
If the return value is "true", the transition was executed successfully. A "false" return value means that the transition failed. In this case check the log for additional details.
Note |
---|
Starting with version 2.5.3, autotransitions are executed after the script has finished. |
...
Since we do not know the result of the operation at the time the routine is called inside the script, it will return "true" by default. |
Example
Example 1
Code Block | |
---|---|
js | autotransition(121, "PRJ-123");
|
Returns "true" if the transition with the ID=121 for the issue PRJ-123 was executed and "false" if if the transition wasn't executed.
Note |
---|
Starting with version 2.5.3 will always return "true". |
Example 2
Code Block | ||
---|---|---|
| ||
autotransition("Require information", "PRJ-232");
|
Returns Returns "true" if the transition requirng information for the issue PRJ-232 was executed and "false" if the transition wasn't executed.
Note |
---|
Starting with version 2.5.3 will always return "true". |
Notes
Note |
---|
|
Frequent Problems
Problem: When executing an autotransition, it fails with the message: It seems that you have tried to perform a workflow operation (<Transition_Name>) that is not valid for the current state of this issue (<Issue_Key>). The likely cause is that somebody has changed the issue recently, please look at the issue history for details.
Solution: Set the skipStateCheck parameter to "true".
See also
Filter by label (Content by label) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|