It often happens that our customers require custom transitions that will change some values on an issue, or take action based on those values without advancing it through the workflow. This usually required identical transitions to be created for every step of the workflow, which is time-consuming as well as difficult to maintain.
We decided that we could use our own Simple Issue Language to create custom actions, similar to transitions, that are flexible and also reusable, making maintenance a breeze.
The Blitz Actions use 3 SIL scripts each:
- The condition script. This decides whether the action is available for the user to execute, or if it is visible to the user but not executable, or if it is simply hidden with no visual indication that it exists.
- The screen script. This decides if an action requires some user input before the action is executed. It allows the administrator to generate a form with fields that will provide input to the actual execution of the action.
- The action script. This is the script that does all the work after all input has been gathered.