| Section | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Copy Value From Other Field Post-Function
Description | The 'Copy Value From Other Field' post-function copies the value of one field to another field, after a transition has been completed. Either within the very same issue or from parent to sub-task. |
Configuration | You must specify the field to copy from, and the field to copy to. For example: |
Example | A workflow is configured so that the 'Resolve' transition has the 'Copy Value From Other Field' post-function. The function is configured to copy the value of the 'Assignee' field to the 'TextField' field. If a user resolves an issue on this workflow, the value of the 'Assignee' field will be copied to the 'TextField' field after the issue is resolved. |
Update Issue Custom Field Post-Function
...
Description
...
The 'Update Issue Custom Field' post-function updates a custom field to a specified value, after a transition has been completed.
Since version 1.4.10, you may optionally append that value to the field its existing contents, or if the field is allowing multiple values, like a multiple selection field, the option matching the value will be set, without unsetting other options. The same is true for label or version picker custom fields.
...
Configuration
...
If you use
%%ADD_CURRENT_USER%%
as the custom field value (exactly this, nothing more), the user who triggered the post function will be appended to the existing field content. Obsolete since 1.4.10, please use append option instead and CURRENT_USER macro.
Additionally for Cascading Select fields, you may either use the value of the option you would like to set, or it's id. In either case, no need to specify the parent option. For example:
- Vehicles
- Car
- Train
- Bus
- Buildings
- House
- Skyscraper
Using Vehicles as the parameter for Custom Field Value would set the custom field content to that very option. Same if you would choose Train. Or, assuming 10701 is the ID of House, then the option House will be set.
...
Example
...
A workflow is configured so that the 'Start Progress' transition has the 'Update Issue Custom Field' post-function. The function is configured to set the 'Location Select' field to 'Sydney,Australia'. If a user starts progress on an issue on this workflow, the value of the 'Location Select' field will be set to 'Sydney,Australia'.
Clear Field Value Post-Function
...
Description
...
The 'Clear Field Value' post-function clears the value of a specified field, after a transition has been completed.
...
Configuration
...
You must specify the field to be cleared. For example:
For information on how to configure a post-function in JIRA, see the JIRA documentation.
...
Example
...
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This is the JSU for Jira Server/Data Center documentation. If you are using JSU on Jira Cloud, see our JSU Cloud documentation. |
Post functions modify data in Jira after a transition is performed. When editing a workflow, you can define which transition triggers the automation. Transitions have essential post functions that are part of Jira. Add-ons like JSU provide additional post functions to help you extend Jira and create powerful automations.
To add a post function to your workflow rule:
Create a draft version of your workflow.
Select your transition, then select the Post Functions tab. Existing post functions for the transition are listed.
Select Add Post Function to display a list of available post functions.
Select the required post function, then select Add at the bottom of the page.
JSU provides the following post functions:
| Child pages (Children Display) |
|---|
See JSU General Configuration for guidance on the settings and parameters that are common to most JSU post functions. To learn more about workflow post functions in Jira, see Atlassian’s Advanced Workflow Configuration documentation.