| Button handy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
When Jira Cloud was launched custom conditions and validators didn’t even exist. This is because they completely break the design of the cloud architecture. Performing an action in the cloud sets off a chain reaction of micro-services and events all at once, like knocking over multiple rows of dominos. Conditions and validators require a pause in those events while they determine if the domino should fall over or if it is allowed to fall over. It really doesn't work like that so instead of being able to use scripted conditions and validators Atlassian release the expressions language which is the only available way to create custom conditions and validators.
...
SIL is easier to write compared to Jira expressions
SIL is easier to read compared to Jira expressions
SIL is easier to test compare to Jira expressions
SIL Listener or
...
Action script
In this example this script should be placed on the “Complete” transition for the subtask workflow. However, this script can also be used as a listener script that is trigger when the issue is updated.
...
| Code Block |
|---|
JSON.stringify(issue.properties['passCondition']).includes('true') |