List of Post Functions
With this post function you can add all values/options from a single- or multi-option field into another multi-option field (on the parent).
Supported fields
Use case examples:
Note that, in some cases you might better use our copy functions (see below) to copy the complete state (all checked/unchecked options) into another field instead of merging.
Add/set/check one or more specific values in a multi-value field.
Supported fields:
Note: You can set single value fields like single-select with the Update/set custom field to predefined value post function.
With this post function you can add an additional comment on a workflow transition.
With this post function you can add an additional comment to linked issues on a workflow transition.
With this post function you can add or remove watchers from a (multi) user picker custom field. This has been a highly requested feature since 2004, see JRA-5493.
Usually setting watchers is a manual step after the issue creation or workflow transition. With this post function you can set them in one single step.
You can combine this feature with our required fields validator and force a user to name a watcher. For example you could set a field "Reviewer" required so that a user must nominate a reviewer in a certain workflow step.
A common use case is to combine the functionality "Add Watcher" with the "Default Values for Create Issue screen". That way you can predefine default users which should be added as watchers to the issue in a defined custom field (multi user picker). On the "Create" transition you can add the post function "Add / Remove Watchers" and all the selected users in the custom field will be automatically added as Watchers.
Note: If the user already exists in the watcher list, he won't be added twice. In addition the post function will add only those users that have the permission in that project.
Add one ore more labels to the current issue. Multiple labels are separated by a comma.
Note: If one label is already set, it will not be added again. Label(s) that don't already exist will be created.
Choose the post-function "Set assignee to specific user" and type in a specific username. Ensure that the user has the permission assignable user.
Assign the issue to a user which has been set in a custom field.
Add a user (e.g. reporter, assignee, creator or any user picker custom field) to one or more group(s).
A common use case is to automatically assign new employees to one ore more group(s) on a transition.
Note: Due to security reasons, group(s) with admin permissions are not available for selection.
Clear one ore more field values on a transition.
Copy field value(s) from or to related issues.
Relation
Scope
Do not overwrite
Run as user
Field selection
You can add 1-n fields, where "Copy from" represents the source field and "to" the target field.
Please note that the chosen fields have to be compatible.
Are you missing a system or custom field? Please contact our support and we will try to help you.
This post function is deprecated and replaced by the Copy field value(s) between related Issues Post Function. Please update your existing configurations. Please note that it's no longer possible to add new configurations. |
This post function is deprecated and replaced by the Copy field value(s) between related Issues Post Function. Please update your existing configurations. Please note that it's no longer possible to add new configurations. |
This post function allows you to copy field value to all issues linked by a certain link type and direction.
This post function can copy all of your existing issue attachments to the issue which is linked to it.
Choose one or more link types that are feasible. Choose the link direction.
After the transition has been processed all attachments will be copied from the linked issue.
In case multiple issues are linked, no duplicate attachments will be copied.
Create new issues during a workflow transition. This post function enables you to realize automated issue creation for many use cases:
Features:
In JIRA, "Assignee: automatic" means tht the issue will be assigned to the first component default assignee or project default assignee.
Further options include:
Create Sub-Tasks on Transition:
A post function that updates or removes a field value during a transition to a pre-defined value.
To define a default value during a transition you can use the option "Do not override" and only set the value if the user did not provide any. (note that you can also define default values on create screens with Workflow Essentials)
Supported field types:
Note: To add values to multi value fields, use the post function Add value(s) to multi-value fields
This post function allows you to transition linked issues.
This post function allows you to set security level on an issue during a transition.
This post function allows you to realize decision gateways or automatically forward an issue to a subsequent status based on conditions.
Basically, you can realize scenarios like:
Follow theses two steps to implement your gateway:
Example:
Let's say you want to automatically approve issues, if the value of a custom field "budget" is smaller than 100 Euro. Your workflow is looking like the one to the right.
Example workflow:
Configuration Options: