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

Add due date automatically based on start date

Mateusz Slifirczyk

Hey,

I've been adding some automation to have the due date be filled in automatically based on the start date. I've noticed though that the same rule will apply to every due date field within the Epic. So for example, if I set it so that the due date is 5 days after start date, it will be like this for every sub-task and child issue. This isn't ideal when different tasks need to have different deadline lengths. Is there a way to make it so that I can have separate rules for each? One method I can think of is having to make a custom field due date for each tasks and set the rules for each, but maybe there's an easier way?

Thanks for the help in advance.

Accepted answers

Evgenii

Hi, @Mateusz Slifirczyk

You can have one rule, but you'll need to set there chain of IF/ELSE conditions, to configure due dates, depending on issue type.

All comments

Rebekka Heilmann (viadee)

Can you post Screenshots of the Automation rule(s) you created?

Evgenii

Hi, @Mateusz Slifirczyk

You can have one rule, but you'll need to set there chain of IF/ELSE conditions, to configure due dates, depending on issue type.

Mateusz Slifirczyk

I see, so this would make it so that a task would have a different deadline length than a sub-task for example, which is already some progress. If I was to have it based on individual issues though, would that then require more rules and custom fields?

Rebekka Heilmann (viadee)

What exactly are you trying to achieve @Mateusz Slifirczyk ?

Are you trying to calculate a due date based on start date and estimated time needed? In your question, you mentioned "5 days after". Is that a set timeframe for all issues or does that vary from issue to issue? If so, you need that information somewhere.

You can use the System fields: Start Date, End Date, Estimated Time.

Rather than having your automation scheduled, it can get triggered by issue changes. You would then have to check, whether any field of your interest has been changed. If the logic is the same for all issue types, you then don't need further if-conditions.

Evgenii

If you want to use automatically triggered rule, then you'll need to make different conditions (or different rules).

There is another workaround, if you want to trigger change manually - you can select "Manually triggered" rule, and show field to input required number of days there.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud