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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,559,353
Community Members
 
Community Events
184
Community Groups

Updating an issue's due date based on sub-tasks' due dates and statuses

I have an automation that sets the due date of an issue to the earliest due date among its sub-tasks. However, I would like it to update when a sub-task is marked as done to the earliest due date of a sub-task that does not have the status 'done'. I tried it this way, but it does not seem to work:

jira2.jpg

jira3.jpg

1 answer

1 accepted

2 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 01, 2023

Hello @Aleksandra Gregec 

Welcome to the Atlassian community!

Can you show us the rule you are using to originally set the due date of an issue to the earliest due date from its subtasks? 

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 01, 2023

This rule will set the parent issue Due Date to the earliest Due Date of its sub-tasks that are not in a Done status. It will run when a sub-task status is changed to Done.

TRIGGER: Issue Transitioned
To Status: Done
CONDITION: Issue Fields Condition
Field to monitor: Issue Type
Condition: equals
Value: Sub-task
FOR BRANCH: Parent
ACTION: Lookup Issues
JQL: parent={{issue.key}} and status != Done
ACTION: Edit Issue
Field: Due Date
Value: {{lookupIssues.duedate.min}}

Hi Trudy, thank you very much! This was very helpful and it works :) Previously I used to set an automated comment when an issue transitions and that would trigger another automation which then changed the due date of the issue to the earliest one of the subtask, by setting it to  {{isse.subtasks.duedate.min}}. I also discovered lookup later but was missing this part parent={{issue.key}}, so all of the subtasks were taken into consideration. 

 

This helped and it works now, thanks!

Like Trudy Claspill likes this

Suggest an answer

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

Atlassian Community Events