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 5 Next »

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

Configuration

Fields

Define and configure the fields to be updated. Each field has the following parameters:

Value

Select how to set the field value. Several options are available, e.g., Copy field value from current issue.

Field

Select the filed to copy from

Additional option

You have the option Write protection (do not overwrite existing values).

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 selected issue link types will be read.

The following options are available:

  • is blocked by (Blocks) -inward
  • blocks (Blocks) -outward
  • is cloned by (Cloners) -inward
  • clones (Cloners) -outward
  • is duplicated by (Duplicate) -inward
  • duplicates (Duplicate) -outward
  • relates to (Relates) -inward
  • relates to (Relates) -outward
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.

The following options are available:

  • Task
  • Sub-task
Filter by status

Leave blank for all issue statuses.

The following options are available:

  • In progress
  • To do
  • Done
Filter by field value

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

You can try your expression by clicking the run button on the top right of the JQL 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

Choose which user* will be able to execute this post function. By default, it is set to the Current user.


Use cases and examples

Title
No content found.

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