It often happens that our customers require Our customers often request custom transitions that will would change some certain values on an issue , or take action based on those values without advancing it the ticket through the workflow. This usually required identical transitions to be created for every step of the workflow, which is was time-consuming as well as difficult to maintain.
We decided that we could use our own Simple Issue Language SIL to create custom actions , similar to transitions, that are flexible and also reusable, making thus reducing maintenance cost and making development and configuring a breeze.
The actions are based on a custom field. This makes them easy to use and also benefit from the already existing Custom Field Context configuration available with JIRA.
The Blitz Power Actions use 3 the following SIL scripts each:
- The condition script . This decides — defines whether the action is available for the user to execute , or if whether it is visible to the user but not executableunavailable for execution, or if it is simply hidden with no visual indication that it existsnothing visible on the UI.
- The screen script. This decides if — defines whether an action requires some certain user input before the action is executed. It allows enables the administrator Admin 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.