- Creating a script
- Connecting a script with a workflow
- Create a test version of script
- Starting a test version
- Test Settings
- Scripts Import / Export
The Groovy Templates feature allows you to create your own personalized scripts. Thanks to them, a administrator has a lot of options about adding individual dependencies to a workflow.
Created scripts can apply to conditionals, validators or post functions.
In addition, an important function of the app is the possibility of creating new versions of scripts, which before activation can be independently and non-invasively tested in a selected and limited environment.
This means that a administrator doesn't have to overwrite a script and test its operation on all projects that use a given workflow, and instead of that he can create a separate, additional test version that will only work on a project, user group or labels selected by him.
Creating a script:
To go to a script creation screen, enter the 
and choose Issues.
In the left navigation bar in the Workflow section, select Groovy Templates.
Script creation starts with Add Script, then choose its type and set a name.
In the next step there will be a console, where a administrator can enter the script.
After the editing is complete, a administrator decide the script should be:
a) activated now - click Save and Activate,
b) tested first - click Save.
Connecting a script with a workflow:
The activated script should be connected to Workflow.
To do this, go to the Workflows tab, then edit the selected Workflow. At this point, select the Transition edition whose script operation should apply to and select conditions or validators or post functions.
After go to the list of possible to add functions, select from the list: Groovy Template Conditions / Validators / Post functions.
Next from the list of created scripts, select the one to be added.
Create a test version of script:
Administrators have the option of creating next versions of scripts and testing them on only the projects, group of users or labels they choose.
To start testing the new version of the scripts a administrator should:
- next to the selected script, go to New version,
- describe the new version (eg 1.1),
- make changes to the script,
- press Save,
or
- next to the selected script, go to New version,
- make changes to the script,
- press Save as new version
- describe the new version (eg 1.1).
Starting a test version:
To perform the test:
- click Version button of the selected script to show all its created versions,
- with the version to be tested, press Test,
- go to Test Settings to set the dependencies of the tested transitions.
In the selected script only one version can be active and only one can be tested.
The active and tested version is always at the top of the list.
Test Settings:
Thanks to this function, it is possible to set parameters (project, group of users and labels), for which scripts tests will run.
Test Settings work globally, which means that they apply to all tests performed for all scripts. However, admins can edit them at any time.
To be able to run tests on a larger database, you can use the function of Any of the following, which allows you to run tests in all combinations of given data.
Scripts Import / Export
The administrator can additionally import external scripts to the application and export all those out of the app.