Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT workflow functions

JWT remote actions

JWT automation rules

JWT calculated fields

JWT calendars

JWT properties

JWT JQL functions

Cloud migration hub

Additional product info

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

This post function allows us to update one or multiple issue fields in linked issues or sub-tasks. 

By default, only linked issues will be updated. If also (sibling) sub-tasks should be updated, the specific checkbox in the "Additional options" section has to be checked.

Configuration

Fields

Define and configure the fields to be updated. For each field you can select:

OptionDescription

Copy field value from current issue


Set field value manually (parser expression)

Enter a valid parser expression

  •  -
Additional option

You have the option Write protection. When selected the field won't be overwritten, if it isn't empty.

Filter

Use the filters to specify which issues will be updated.

The filters are AND concatenated. So in order to update an issue, it must fulfill every set filter.

Filter project

Filter your project by choosing from one of the following options:

  • Any project
  • Current project
  • Any but current project
Filter by issue link type

Only issues linked to current issue by the selected issue link types will be udpated.

This field is required.

Filter by issue type

Selected issue types will be read, but if you don't select any, it won't be applied any filter by issue type. In that case, all the issue types will be read.

Filter by status

Select issue statuses that must apply to the issue in order to be updated.

Leave blank for all issue statuses.

Filter by field value

Enter a logical parser expression . The expression must return  true or false

Additionally, field codes can be entered.

You can try your expression by clicking the run button on the top right of the expression box.

Additional options

The following options are available:

  • Update sub-tasks fulfilling conditions on issue type, status, and project - This option only makes sense when the current issue itself is not a sub-task.
  • Sibling sub-tasks have the same parent as the current issue. This option only makes sense when the current issue is itself a sub-task.
  • Issues and sub-tasks transitively linked and fulfilling conditions will also be updated. Issues are read recursively without depth limit, but each selected issue is only read once.
  • Notifications will be sent according to the associated notification scheme.
  • A specific entry will be created in issue history for this field writing.
Conditional execution

You can optionally specify a logical expression 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

Run as

Unable to render {include} The included page could not be found.


Use cases and examples

Title
No content found.

If you still have questions, feel free to refer to our support team.