You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
This thread explores how you might go about that.
(Tip: using the community search, in this case for "automation remaining", can help uncover answers more quickly.)
But I really suggest you consider this question first: Do you really want to automate that?
I see the biggest value of the Remaining Estimate field to be having a human re-evaluate that whenever time is logged. Why? Because usually the Original Estimate is wrong.
Having been a developer, and having had to estimate my work, and then log my time, we know this to be true empirically. Any Original Estimates is a guess based on incomplete information.
Consider this... If I thought a Story was going to take me 3 hours, but it only takes me 1 hour, I would log time for 1 hour, set the Remaining Estimate to zero, and transition the issue onward.
Do you really want to bake into your process that instead the issue will get auto-set to "2 hours remaining" after logging that first hour? How many of your remote employees might see that as an opportunity to watch a few more episodes of their favorite show, instead of working on something else? My point is: that's a bad process.
If you really don't care about Remaining Estimate, maybe don't use it at all?