This post-function can set multiple values for selected fields of an issue. The value can be provided either as text (with optional Nunjucks annotations) or as a JSON value.
To add a post-function:
Log into your Jira Server instance as an Administrator.
Click on the Administration icon ⚙️ in the upper right corner.
Select Issues.
In the left-hand panel, click Workflows.
Click Edit for the workflow to be edited.
Edit the Transition:
When viewing the Workflow in Diagram view, select the Transition and click the Post Functions link. Click Add post function at the top of the list of existing post functions.
When viewing the Workflow in Text view, click the name of the Transition then select the Post Functions tab. Click Add post function at the top of the list of existing post functions.
Configure the post-function
Follow the steps above to add a post-function to a Transition.
From the list of post-functions, select Set issue fields.
Click Add.
The Set Issue Fields page will open (Figure 1, right). Configure the post-function as needed, setting the options for user to assign, the assignment behavior, and additional options as necessary. See below for details on each of the configurations.
Click Add.
Note that you need to publish the workflow for the new post-function to take effect.
Target Issue(s)
The Target Issues configuration set which issue will be updated by the post-function.
Which issue(s) - Select the issue type.
Current Issue - The issue that is being transitioned and triggering the post-function.
Issue/Subtask
Sub-tasks of the current issue - Updates will be made to all sub-tasks of the current issue.
Parent issue of the current sub-task - Updates will be made only to the parent of the current issue (if any).
Epic/Story
Issues that belong to the current Epic - Updates will be made to all issues that belong to the current Epic.
Epic of the current issue - Updates will be made only to the Epic of the current issue (if any).
Portfolio Parent/Child
Child issues of the current issue in the Portfolio hierarchy - All child issues will be updated.
Parent issue of the current issue in the Portfolio hierarchy - Only the parent issue will be updated.
Issue links
Issues linked to the current issue through any link type
Issues linked to the current issue through the following link type
JQL / Groovy
Issues returned by the following Groovy script
Issues returned by the following JQL search
Issue Link - Only available when Which issue(s), above, is set to Issues linked to the current issue through the following link type. Select the required link type between the current issue and the issue to be updated.
Groovy script - Only available when Which issue(s), above, is set to Issues returned by the following Groovy script. Enter a Groovy script that returns the ID values for the issue or issues to be updated. See Customizing further with Groovy scripts for more information on Groovy scripting.
JQL expression - Only available when Which issue(s), above, is set to Issues returned by the following JQL search. Enter a JQL expression that returns the ID values for the issue or issues to be updated. See Using JQL in JMWE for more information on JQL.
You are viewing the documentation for Jira Server / Data Center.
On This Page
Set fields
The Set fields section determines which fields will have their values set, and the values to use. The section includes two parts - the Add field menu where you select issue fields, and the list of fields that have been configured for your post-function.
Add field - Select a field from the pulldown menu to open a configuration panel (Figure 2, right).
The Add field configuration panel (Figure 2, right) enables configuration of the field value.
Field - The field being configured.
Options - Select additional options for the field:
Set only if field is empty - Set the field value only if the field is currently empty.
Create missing values - Create missing Components, Versions, or Options in the destination project. Only applies to compatible fields.
Ignore empty values - Don’t clear the field if the value is empty or null.
Add source value(s) to destination field - Add values from the source field to the destination field. Applies only to multi-valued fields.
Remove source value(s) to destination field - Remove values in the source field from the destination field. Applies only to multi-valued fields.
Field value - Configure the value for the field when it is set by the post-function. The value can be any value returned by either a Groovy Script or a Groovy Template.
The table of fields includes a few columns:
Field name - The name of the configured field.
Options - A list of any options selected during configuration.
Value - The Groovy script or template that returns the field’s value.
Actions
Edit (
) - Use the Edit button to open the Edit field configuration panel where an existing field configuration can be modified. Click Update to save the new configurationDelete (
) - Remove the field from the post-function.
Global options
Set the behavior of the post-function.
Send notifications - Enable Jira to send notifications when it executes.
Conditional Execution
In addition to the Assignment behavior settings, it is possible to configure the post-function to execute (or not execute) only in specific circumstances. The Condition execution options set these behaviors.
The options are:
Only if condition is true - Check this option to execute the post-function based on the result of a groovy expression. See Conditional execution/validation using a Groovy expression for more information.
Condition - Enter a Groovy expression that evaluates to
trueorfalse(or truthiness/falseness).
Run as
Select which user account will be used when running the post-function.
Run as user
Current user - The user who triggered the transition.
Specific user - Select a specific user account to execute the post-function.
User in field - Select a User Picker field or other custom field containing user values.
User from script - Enter a Groovy script that returns a user ID.
Examples:"jdoe"- To use a static value username.issue.get("assignee")- To return the current issue's Assignee.
Note: Prior to JMWE 8.4.0, this configuration stores a username value. If an Administrator changes a user’s username, the post-function will fail.
Existing post-functions created before version 8.4.0 should be updated; open the post-function for editing and save it (no changes are necessary). This will update the configuration to use the immutable user ID value.
New post-functions do not need to be updated.
Error Handling
Make transition fail when an error occurs in this post-function - Select this option to make the transition fail when an error occurs while running the post-function. An error message is displayed to the user showing the transition failure.
By default Error handling is turned off. When it is turned off, all errors (Java Exceptions) raised by this post-function, including those raised by custom Groovy scripts, will be logged in the JIRA log file. However, they will not be reported to the user and will not prevent the transition from completing.
When designing new workflows or troubleshooting them, it may more convenient to be notified immediately of any such error during the execution of the transition. For example, on production Jira instances you might want to show errors only for the post-function(s) being created or updated, in order to avoid disrupting other workflows. To make errors raised by the current post-function prevent the transition from completing and show the error in the browser, select Make transition fail when an error occurs in this post-function.
When the Error handling option is selected on a specific extension, it overrides the configuration on the JMWE configuration page.
If you want to show all errors - to either All Administrators or All Users - configure the option globally on the JMWE configuration page. For example, on development and staging instances, you can activate error reporting for all JMWE post-functions so as to display all the errors (it is recommended to do so); on production instances you may want to activate error reporting only for administrators so that they can be made aware of configuration errors.
