nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Aleksandra Gregec

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:

Accepted answers

Trudy P Claspill

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?

All comments

Trudy P Claspill

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 P Claspill

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}}

Aleksandra Gregec

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!

KL_1cyuri

@Aleksandra Gregec LIFESAVER!! I've googled endlessly for this exact smart value logic because I don't have Lookup Issues component

{{issue.subtasks.duedate.min}}

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud