...
| Warning |
|---|
Looking for the documentation on the newest versions of Power Actions for Jira 8? Click here and leave these dusty old pages behind! |
Power Actions™ wizard is implemented as a list of steps starting that start from the main button. They can all be configured directly from the configuration page of the custom fieldYou can configure them on the custom field configuration page.
The configuration page displays a list of buttons with all their steps. A button is actually the first screen of a the wizard.
For every button you can do the next following operations:
- edit the scripts
...
- – condition, screen, and action
...
- change the description
...
- rename it
...
- add or remove a step
...
- reorder the steps to suit your needs.
When adding a next step to a given button, a new line will be added in the configuration table, containing the it. For this new step we also configure the scripts, change the description or rename it.
The steps of a button can be reordered inside the button.
Adding new steps
In order to add a new step all you need to do is press the ", click the Add Next Step" button (the "+" icon) for the desired needed button. A new line containing the new step will be added into the with a step is added to the configuration table.
The name of the step will always be built from starts with the word "Step" and its position in the list. This is an non-editable data .The but for your convenience, you can change the description of the step can be changed by clicking on the "by clicking Change Description" button.
For each step you can also configure the scripts.
| Note |
|---|
| The added steps can be reordered within the You can reorder the steps within a button, but the steps step names will be always retain the current position of the step. |
Configuring a step
The condition script for a step is similar to the one for a button. This means that it still allows you to , you can decide whether an action will should be available for the user , or not. By default, when adding you add a new action, it will have the following default condition script.
...
The script should return one of the predefined variables: ENABLED, DISABLED, DISABLE or HIDDEN.
...
The main difference between the condition script for a button and the condition script for a step is how we interpret the
...
DISABLED / HIDDEN values.
- Enabled actions are visible and available for the user to execute.
- Disabled and Hidden actions Disabled actions mean that the screen for the action will not be visible at all and thus not available unavailable for the user to execute. There is basically no difference between returning disabled or hidden.
...
- Hidden actions mean that the screen for the action will not be visible but the action script will still be executed
Of course, with the help of Simple Issue Language (SIL), the return value of the script can be conditional.
| Code Block |
|---|
number ENABLED = 1;
number DISABLED = 2;
number HIDDEN = 3;
if(<some_condition>){
return ENABLED;
}
if(<some_other_condition>){
return DISABLED;
}
return HIDDEN; |
Sharing values between wizard screens
Since some values from the screen of the wizard may be You can configure a wizard so that certain values on the wizard screen depend on other values from another screens, we implemented some . For this we implemented additional routines that should help with the sharing mechanism.