Automate start date of sub-task based on previous sub task due date

Mateusz Slifirczyk March 13, 2024

Hi,

I'm wondering if it's possible to automate the start date of a sub-task based on the due date of previous sub-task. For example, I want the 2nd sub-task to have a start date of the day after the due date of the first sub-task.

1 answer

0 votes
Kalyan Sattaluri
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 Leaders.
March 13, 2024

Hello @Mateusz Slifirczyk 

  • Will the total number of sub-tasks be constant or can it be varying number?
  • When is the first sub-task due date populated?
  • How do you decide what is the next sub-task?

One way I can think of is a scheduled rule which does this one sub-task at a time, its convoluted but need above clarifications.

Mateusz Slifirczyk March 13, 2024

Hey @Kalyan Sattaluri 

 

There are three Epics that are used as templates (we clone them for new projects). Sub-task are mostly same in number with one template having one more.

The due date is populated when the start date is set.

The sub-tasks are done in order, one after another.

Kalyan Sattaluri
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 Leaders.
March 13, 2024

Hello @Mateusz Slifirczyk 

Epics dont have sub-tasks.

I am guessing these epics have stories and those stories have sub-tasks?

How is start date and due date of sub-task 1 selected? Is it manually populated or will it need to be from the story?

Also, Sub-task 2 start date is task 1's due date, but what should be due date of sub-task 2? Is it a fixed number of days from start date?

Can a due date of sub-task be changed?

Sorry about asking all these questions but to develop a rule, we need all these details..

 

Mateusz Slifirczyk March 13, 2024

@Kalyan Sattaluri - It's fine, I really appreciate the support!

I think it was just confusion in terminology. So I've got Epics which then have Tasks. At the moment, the start date is populated when the status changes, and the start date triggers the due date which is calculated based on that which option is selected in a drop-down (I have a few options with different SLAs so I use a drop-down to be able to differentiate them).

The tasks at the moment have the same automation and also a drop-down which tells Jira which number of days to use based on the option.  This works, but I was wondering if it can be taken a step further and from just populating the Epic, I could get the dates to be filled in for the tasks.

It can be a little confusing, I hope this makes sense.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events