Update fields | Decadis App Help Center

The Update fields post function automatically updates a single or multiple issue fields on one or multiple target issues.

Additional field values can be inherited or manually set using the JWT expression editor.

🛠️ Configuration

Target issue

The issues to be updated. If a list of issue keys is passed, the update will be performed for every issue in the list.
The following options are available:

Current issue
Parent issue
Parser expression

When the option parser expression is selected, an expression parser input field is displayed and the input has to be an issue key or an issue list. Every issue in the given list will be updated.

Fields

Every supported field can either be set or cleared.

After selecting a field and clicking the Add button, you can select in the popup how to set the value. There are three or - when dealing with selectable fields - four options:

Copy field from current issue
Clear field value
Set field value manually - Read more about the JWT expression editor
The option Selected value is available for the following fields types:
- Jira Software related fields like Sprint or Epic
- User related fields like Assignee or Reporter
- Version related fields like Affects- or Fix version/s
- Component/s
- Labels
- Priority
- Resolution
- Security level
- and all option based custom fields that are supported

Attachments

The Attachments section allows you to define which files from the current issue should be copied to the defined target issue(s).

You can choose between the following options:

Option

Description

All attachments

Select this option to copy all attachments from the current issue. You may limit it further by selecting specific file types (e.g., .docx, .pdf) from the document type dropdown.

Attachments filtered by regex

Enter a valid regular expression (e.g., .*\.png) to filter attachments by filename pattern. Only matching files will be copied.

Regular expressions are accepted with or without slash delimiters and regex options, e.g. .*\.png or /.*\.png/i (to accept mixed case file extensions), but not /.*\.png (missing final delimiter).

Attachments selected via parser expression

Use a JWT or Jira expression to programmatically define which attachments to copy. This allows for dynamic selection based on issue data, metadata, or business rules. For example, you can copy only attachments added by a specific user, those added after a certain date, or those with matching custom field values.

Transition attachments

Select this option to copy all attachments uploaded during the transition via the "Attachments" field. You may limit it further by selecting specific file types (e.g., .docx, .pdf) from the document type dropdown.

Only attachments uploaded through the Attachments field on the transition screen are supported.

There is a size limit for copying attachments. If any attachment exceeds 10MB, it will not be copied.

Copying of attachments might also fail due to a network error in the Atlassian infrastructure, e.g. when copying large amounts of attachments - please check the log, if you miss attachments in the copy target.

Run as

Select the user that will be used to execute the post function. By default, it is set to the current user that executes the transition.

The following options are available:

Option	Description
Selected user	Select a specific Jira user.
User in field	Select the field containing the user that will be used to execute the post function.

The configured user must have all necessary permissions to edit the target issue. When using the Jira Workflow Toolbox app user, this requirement is always fulfilled, as the App user has the required permissions.

Additionally, using the Jira Workflow Toolbox app user makes it possible to set or update fields even if they are not present on the screen. The Jira Workflow Toolbox app user can also modify issues that are normally restricted from editing.

Conditional execution

You can optionally specify a logical expression or a Jira expression depending on the chosen Parsing mode to define the circumstances (or conditions) under which the post function should be executed.

The result of the logical expression must return a boolean value of either:

true → the post function will be executed
false → the post function will not be executed

Using the conditional operator, even complex or multi-layered conditions can be constructed.

Make sure to learn more about defining logical expressions and browse through the various examples here: Logical mode

📚 Use cases

Use case	Workflow function	Parser functions	Use case description
Set the due date based on the priority	Update fields	getMatchingValue()
Obtain the difference between two dates	Update fields		Update a number field with the difference in days between two dates obtained from two Date Picker fields.
Assign an issue to the user who last commented on it	Update fields		Assign the issue to the user who last commented on the issue.
Add three days skipping weekends automatically to a Date Picker	Update fields		Add three days to a Date Picker field from the current date.
Keep parent's priority in sync	Update fields		Set the priority of the parent issue to the priority of the current issue.
Set the assignee based on the issue type	Update fields	getMatchingValue()
Set the fix version to affects version when resolving an issue	Update fields		When an issue is resolved and the resolution set to "Done" the Affects version/s will be added to the Fix version/s field.
Use the app user to update non-editable fields	Update fields		Update an locked issue in the Done status
Automatically add incident reporters to problem tickets	Update fields	append() fieldValue() linkedIssues() toStringList()	In our Jira Service Management project, we want to automatically add the reporter of an incident to the corresponding problem ticket.
Copy labels of a sub-task to the parent issue upon closing	Update fields		When a sub-task is closed, the labels of the sub-task will be added to the Labels field of the parent issue.
Assign an issue to the project lead, if the issue is unassigned on creation	Update fields		When an issue is created without an assignee selected, the issue will be assigned to the project lead of the project.
Add watchers from another field	Update fields Transition issue	union() toStringList()
Add a sub-task's summary and key to the description of its parent	Update fields		When a sub-task is created, its summary, issue key and date, and time of creation will be added to the description of the parent issue.
Set a date field to a future date	Update fields	dateTimeToString()	Set any date field of an issue to a future date.
Record an auditable timestamp of a Compliance Approval	Update fields	dateTimeToString()	Set a Date Time Picker field to the current date
Copy field values from epic to issues under it after creation	Update fields Transition issue	epic() issuesUnderEpic() filterByStatus()	Copy the values of the fields defined in the Update fields post-function to the issues under the epic after their creation.
Set a date field to the current date	Update fields	dateTimeToString()	Set a Date Time Picker field to the current date
Assign important issues to the project lead	Update fields		Automatically assign and issue to the project lead. Issues will only be re-assigned if the priority of the issue is set to Highest to make sure that only important issues are being escalated.
Set the priority to Highest if the 'Infrastructure' component is selected	Update fields		When an issue is created with the "Infrastructure" component selected, the priority will be set to "Highest".
Background priority calculation	Update fields	avg()	Automatically set issue priority during creation using the average of two custom fields. Since the field is only visible on the view screen, the automation must run as the App user to bypass editing restrictions.