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

Compare with Current View Page History

« Previous Version 3 Next »

On this page


In this documentation and the post function configuration you will notice the symbol ( * ) next to some parameters, it means that this field is mandatory and shall not be left empty. Fields without the symbol are optional.

Basic configuration*

Below you will find a detailed description of each parameter of the basic configuration of the function.

Target field*

Add a field to configure

Value*

Select how to set the field value. The following options are available:

Copy field value from current issue

Then you can choose the Field* the copy from.

Set field value manually (parser expression)

Then enter the Expression*

And as an additional option, you can choose Write protection to 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

Additional options
  • Read also subtasks fulfilling condition on issue type, status and project - This option only makes sense when the current issue itself is not a subtask
  • Read also sibling subtasks fulfilling condition on issue type, status, and project - Sibling subtasks are understood as subtasks with the same parent as the current issue. This option only makes sense when the current issue is itself a subtask
  • Read linked issues and subtasks recursively Issues and subtasks transitively linked will also be read, provided they fulfill stated filtering conditions. Issues are read recursively without depth limit, but each selected issue is read-only once
  • Read also current issue - Current issue will be included in the issue selection, i.e., current issue's field value will also be read
  • Update issue immediately - A specific entry will be created in issue history for this field writing
Conditional execution

Enter a condition (Logical / boolean condition) using the JWT expression parser - full feature list syntax.

You can even logically link and gather conditions in expressions as you like in order to map more complex conditions.

The post function will only be executed if the condition is met (returns true).

Run as

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



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