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

Due date not updating when logging work and updating remaining estimate simultaneously

Denys Pavlov_el8234

I’m stuck creating an automation for the use-case where a task’s due date gets automatically updated based on the updated remaining estimate.

I have a task

Start date: 18.11
Original estimate: 8h
Due date: 18.11

I spent 8 hours working and log these 8 hours on 18.11. I see that I need another 12 hours to fully complete the task, so when logging the 8 hours I set the remaining estimate to 12. Based on this, the due date should move from 18.11 → 20.11.

I already have a rule that updates the due date when I manually update the Remaining Estimate field alone, without logging hours.

However, when I log hours and update remaining estimate simultaneously the due date doesn't shift. Seems like Jira doesn't understand that I update remaining estimate and does not update due date.

I've tried various options for my rule, including "Log Work", "Edit work item" but none of these worked for me.

Eventually I ended up with this rule

Screenshot 2025-11-20 at 20.15.39.png

I'd appreciate it if you could help me to configure this automation.

Thanks!

Accepted answers

Rik de Valk (Brainboss)

Hi @Denys Pavlov ,

I had to try this for myself to figure it out.

The Log Work doesn't trigger an issue updated event. As stated in the documents here, the Issue Updated doesn't include the Log Work.

But when I use the Trigger "Work Logged", then my Rule is triggered.
And I can use the {{worklog.timeSpentSeconds}} to calculate the number of days from now is remaining. And then I can compare that with the Due date to determine if an update to the due date is needed.

Hope that helps.

Have a nice day.

Rik

All comments

Rik de Valk (Brainboss)

Hi @Denys Pavlov ,

I had to try this for myself to figure it out.

The Log Work doesn't trigger an issue updated event. As stated in the documents here, the Issue Updated doesn't include the Log Work.

Hope that helps.

Have a nice day.

Rik

Denys Pavlov_el8234

Hi @Rik de Valk _Brainboss_ many thanks for your prompt reply.

When I said “I tried Log work”, I actually meant the “Work Logged” trigger. And it does work — when I log time andupdate the remaining estimate at the same time, the due date gets updated correctly.

However, the Work Logged trigger also updates the due date even when I don’t manually change the remaining estimate.

For example, when I simply log time, Jira automatically reduces the remaining estimate, and this new remaining estimate still gets added to the due date. Do you know what I mean?

So I believe the issue is not with the date-calculation formula itself (thanks again for the hint!), but rather how the time tracking behaves.

Do you know if there is any smart value or mechanism that lets me detect whether the remaining estimate was changed manually, and not just recalculated automatically during work logging?

Thanks

Rik de Valk (Brainboss)

Ah, yes. There is no difference between an automatic versus manual update of the remaining estimate.

This makes the solution more complex.

Find the change in remaining estimate (old - new estimate)
Compare this change to the logged time

If the change is different from the logged time, it must be a manual update.

If the change is equal to the logged time, it must be an automatic update.

To put this in practice:

Getting the logged time is easy. Simply use the trigger Work Logged and get the {{worklog.timeSpentSeconds}}
Getting the change in Remaining Estimate is more challenging. There doesn't seem to be a direct manner to get the change for that. So you'll need to make an API call in your automation.

Here's a good article on how to call a Jira API in an automation
You can use this end point to fetch the Change log /rest/api/3/issue/{issueIdOrKey}/changelog

I found this a nice challenge, so I tested it myself 😄

Trigger: Work Logged
Action 1: Send web request
- URL: {{baseUrl}}/rest/api/3/issue/{{issue.key}}/changelog
- HTTP method: GET
- Web request body: Empty
- ✅ Delay execution of subsequent rule actions
- Headers: Authorization: Basic {your base64 encoded username:pat} (see linked article for how to get this)
Action 2: Create variable
- Name: from
- Smart value: {{#webhookResponse.body.values.last.items}} {{#if(equals(field, "timeestimate"))}} {{from}} {{/}} {{/}}
  This gets the API response and extracts the old time estimate
Action 3: Create variable
- Name: to
- Smart value: {{#webhookResponse.body.values.last.items}} {{#if(equals(field, "timeestimate"))}} {{to}} {{/}} {{/}}
  This gets the API response and extracts the new time estimate
Action 4: Create variable
- Name: change
- Smart value: {{#=}} {{from}} - {{to}} {{/}}
Action 5: Log action (just for troubleshooting)
- Log message: Change: {{change}}. LoggedTime: {{worklog.timeSpentSeconds}}
IF ELSE Block:
- Condition smart value:
  - First value: {{change}}
  - Condition: equals
  - Second value: {{worklog.timeSpentSeconds}}
- Then: do not update the due date. This was an automatic update
ELSE:
- Then: update the due date. This was a manual upate

⚠️ The Change log from API can give many records if an issue was updated a lot. So you'll have to first check the webresponse.total to see if there are more than 100 results. If so, calculate which startAt value you should include in your second web request to ensure you get the latest change records

Screenshot 2025-11-21 at 11.54.19.png

Have a nice day!

Rik

Denys Pavlov_el8234

Hi @Rik de Valk _Brainboss_

Many thanks for your extensive reply — it's good to hear that you found this challenging
It does seem like a very complex task indeed. I'll try to play with it and see how far I can get, and I really appreciate you taking the time to outline the approach in such detail.

Thanks!

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