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

Automation: Custom Date changing Due Date


I have an automation rule that populates the Due Date based on the date that is entered in a custom field called Meeting Date.  I also have a rule, that I would like to update the due date whenever the meeting date is changed.  This rule is set to update several tasks and subtasks within the Epic.  However, it is not working consistently.  Sometimes it makes the updates I would like, but not all the time. Any insight into what I am doing wrong?


2 answers

0 votes
John Funk Community Leader Jan 21, 2023

Hi Alexandra,

I looks like you are trying to update the Meeting Date and then also update the Due Date based on this same Meeting Date value in the same step of the rule. You cannot count on it being done in that order. 

You should have a step to do the Meeting Date update. Then do a New Action for Re-fetch issue. And then do a New Action for setting the Due Date based on this newly updated Meeting Date. 

0 votes
Mark Segall Community Leader Jan 20, 2023

Hi @Alexandra Astor - It looks like your rule is straightforward.  I would recommend cross-referencing the failed updates against the rule log to see if there's something going on.  

The only thing that comes to mind is if some of the issues are not in the same project.  In which case, you'd need to make sure the rule scope (on the Rule Details screen) is set to global/multiple projects. 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events