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

How can I add approver in Jira Software when a due date is changed

Neha Bagtharia_a04unl

I want to add an approver whenever someone changes due date. This due date change should be done with a reason. Whenever anyone tries to change due date, he should add reason then this is sent to approver to accept/reject the changes. This should be managed without any workflow transition and to be purely field level validations.

Accepted answers

All comments

Ste Wright

Hi @Neha Bagtharia

You can't do this natively; there is no approval process for fields being modified.

You could use Automation to notify specific user(s) via email if a due date is changed? They could then review the change, and reverse it if needed.

---

You might also be able to do something more complex with Automation - for example...

First rule...

If a due date is edited
And the user is not an approver
Duplicate the due date into a hidden custom field (eg. Due Date Unapproved)
And reverse the field edit
Then notify the editor it's awaiting approval
And send the approver an email, request approval via a custom field (eg. Approve Due Date)

Second rule...

If Approve Due Date is edited
And Due Date Unapproved is populated
- If it's no, clear Due Date Unapproved
- If it's yes, edit Due Date, then clear Due Date Unapproved

...but this seems complex to me.

---

Aside from this, alternatives would be...

Apps: Check out Apps such as Approval Path for Jira or another App on the Marketplace
Permissions: Limit who can edit a due date? You can do this via permissions...
- Company-managed: Limit who has access to the "Schedule Issue" permission
- Team-managed: Limit who has access to the "Edit any due date" permission

---

Let us know your thoughts

Ste

John Funk

Hi Neha - Welcome to the Atlassian Community!

This is a little more complicated but can be done.

You would need to create a new screen with either a custom field where the user has to populate something, or you could just use the Comments field.

Then add a self looping transition on the status - a transition that starts with the status and ends with the same status. Then add the screen you created to the transition along with a Validator to for Field Required for your custom field or the comments field, whichever one you decided.

Then create a new automation rule for when the field is edited to send an email to the Approver with information in the field.

The transition to the next status would have a condition so that only the Approver can execute it. So for the approval, the Approver just moves the issue to the next status.

Neha Bagtharia_a04unl

Thank you for your reply @Ste Wright I'm trying to automate to populate 2 new fields if due date value is changed. But I am not able to show those fields. I don't want these fields to be shown by default in the form. These fields to be visible only if due date is changed. Is there something I am missing?

John Funk

Can you share the rule that you have so far?

Neha Bagtharia_a04unl

@John Funk the solution seems to be too complicated. Is there any other way around to achieve this? Primary motive is to track due date changes with reason.

Ste Wright

Hi @Neha Bagtharia

The fields don't need to be on a Screen to populate them.

But there's no Automation Rule which would "visualise" those fields based on a due date being changed.

If you want the Fields to be visible, they need to be on the Screen (regardless of the logic).

---

You might be able to do this using an App, such as Scriptrunner for Jira utilising behaviours?

Ste

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