Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Increment custom field based on “is blocked by” linked issues

Avi Morali
Contributor
March 30, 2026

Hi everyone,

I’m trying to create a Jira Automation rule to update a custom field called BlockedTasks in an issue. The goal is to count all issues linked via “is blocked by” and increment BlockedTasks when the linked issue’s status is Done. Specifically:

  • Done → increment BlockedTasks by 100

The rule should:

  1. Reset BlockedTasks to 0 at the start
  2. Loop through all “is blocked by” linked issues
  3. Increment BlockedTasks by 100 if the linked issue is Done
  4. Update the BlockedTasks field in the original (trigger) issue

The trigger for my rule is a status change.

I’ve tried referencing the field using {{issue.BlockedTasks}} and {{triggerIssue.BlockedTasks}}, but I keep getting the error:

 Failed to get value for triggerIssue.BlockedTasks|0.plus(100)

I’m attaching a screenshot of my current rule for reference. image.png

Any guidance on how to properly reference and update this field in the automation would be greatly appreciated!

1 answer

0 votes
Arkadiusz Wroblewski
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
March 30, 2026

Hello @Avi Morali 

the reason this is not working is basically two things.

First, inside a Linked work items branch, {{issue}} is the linked issue, not the original one. Atlassian’s automation docs are clear on that. The original issue is only available there as {{triggerIssue}}. 

Second, branches over multiple related issues run in parallel, so they are not a safe place to keep incrementing the same field on the parent issue. Atlassian explicitly says you cannot rely on changes between parallel branch executions. In practice that means multiple branch runs can read the same starting value and then overwrite each other. 

One more small point for numeric calculations, Atlassian documents the {{#=}} ... {{/}} math-expression format. Your current value is not using that pattern. 

Safer will be probably first run look up on linked issues in done and then set Field.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events