Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jira Automation - Can't reliebly update a field based on trigger



Was wondering if anyone had some ideas on this.

I have a workflow I'm trying to automate, but hitting some problems with getting it to consistently work.

  1. Issue Created, custom field "Name" has a value "foo"
  2. Do JQL to find any issues in this project which also have "Name" ~ "foo"
  3. Link the Created issue with all the issues found in JQL query
  4. Each time an issue is linked, update a custom field "Count of Related Tickets" by +1

I have tried two different ways to do it

First Attempt:



This increments the "Count of Related Tickets" on the linked issues, not the trigger issue (the newly created issue). I need to update the Trigger issue, not the linked issue.


Second Attempt:

This has 2 rules that work off each other.

First rule, links the related issues:


And the second rule does the increment based off the trigger "When issue linked"


But this doesn't work consistently either. It works fine for 1 or 2 linked issues, but if there are 5+ it will not update the number correctly. For example 11 linked cases, then the value should be 11, but the field only gets updated to anywhere between 3 and 8. I can see in the audit log that the Edit Issue Field is all happening more or less at the same time, so it is not always pulling the most recent value. Even adding in the re-fetch issue data doesn't help. I believe the problem is the asyncronous nature of jira updates. If there was some way to make them go FIFO that would be amazing.

Any ideas on what I can do to make this work, or maybe an easier way to do it?




0 answers

Suggest an answer

Log in or Sign up to answer