Update fields based on rules

This very powerful post function can be used to update a single issue field according to a set of rules.

You can use this function to construct multiple "if → then" rules.

Once you have defined the source field, a rule and a value you have constructed the entire if clause.

The next step is to define, which value the target field will be updated to, if the values match. This is the then part of your rule.

Configuration

Source field

Select the field that will be analyzed by the defined rules. The combination of this source field and the source value, as specified in each rule, builds the if part.

Even though this parameter is mandatory, the selection is irrelevant if you choose to base your rule on a Logical expression.

Target field

Select the field to be updated according to the rules.

The first rule matching the given expression will update this field.

Rules

Define the rules for updating the target field and the corresponding target field values. You can choose between the following options:

Option	Description
Text comparison	Choose this option if you want to compare the value of the specified source field with another text value.
Logical expression	Choose this option if you want to construct a logical rule using the Logical mode. Once set up, you have to define, which value the target field will be updated to if the expression returns `true`.
Regular expression	Enter a valid regular expression and optionally use field codes to to specify your rule. This expression will then be evaluated against the selected source field.

Examples:

Source field	Mode	Source field value	Target field	Target field value	Description
IF			THEN		Output
Priority	Text comparison	High	Assignee	a.agrant	If the issue priority is High, the issue will be assigned to a.grant.
Priority	Text comparison	Low	Assignee	d.jones	If the issue priority is Low, the issue will be assigned to d.jones.

Logical expressions are not analyzing the source field. Whereas text comparison and regular expression rules are checked against the source field value, logical expressions are independent of the source field value. Instead you will have to provide a logical expression using the Logical mode.

Alternatively you could use the Update fields post function and set values using multiple conditional operators.

Additional options

Option	Description
Write protection	Check the write protection option if you want to prevent a field to be updated, if it already has a value. If checked, only empty fields will be set.
Evaluate all rules	Per default, JWT will stop rule evaluation when the first rule matches (e.g. a source field value was identified according to a rule). If you check this ption, the other rules will be be evaluated . Only applicable for multi-valued or temporary target fields.
Update issue immediately	Choose to update issues immediately if you want Jira to fire a separate "Issue updated" event for any field change. This will also result in a dedicated issue history entry.

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 case and examples

Title
No content found.

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

Content

Space Tools

Configuration

Use case and examples