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 due-dates when moving the issues

yuliia.soury

Hi!

When moving unresolved issues to the new sprint, the due-dates are left the same. This causes overdue.

Is it possible to make an automation or something else to remind the owner of the issue to change the due-date when the unresolved issue is being moved to the new sprint?

Thank you in advance.

Accepted answers

John Funk

Hi Yulia,

Yes, you can easily create an Automation For Jira rule to send and email for that.

Boris Berenberg - Atlas Authority

We support this in Notification Assistant for Jira Cloud. You would use a Field Changed trigger and set it to the sprint field. In the near future, we will release custom email templates so you can customize the message to the user.

All comments

John Funk

Hi Yulia,

Yes, you can easily create an Automation For Jira rule to send and email for that.

Boris Berenberg - Atlas Authority

yuliia.soury

Thank you!

yuliia.soury

Okay, thank you!

Dave

Hi @yuliia.soury,

Just an observation / question - but I'm really curious to know why you're combining the Due Date with the Sprint field? Are you using the Due Date to represent the planned end date of work or is it being used to represent a deadline?

I'm interested to understand the benefit you get from using the 2 fields together,

Regards,

Dave

Cesar Daldosso

you can use my automation but still remains with a failure when overflow a due date sprint.

Please check it the following

https://community.atlassian.com/t5/Jira-Software-questions/how-to-setup-due-date-with-the-sprint/qaq-p/1815900#M162313

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

jira-cloud