What's the use of time tracking if Jira can't automatically get a countdown for original estimate?

[Rui Caldeira]

I think Jira should have a simple countdown method that should be triggered automatically by status change. Why isn't this implemented? That would be sooo useful!

[Ravi Sagar _Sparxsys_]

Hi @Rui Caldeira 

Well that is because changing statuses (known as transitions) doesn't always mean that the work was done or time was spent (for worklog purposes). Workflow let you define the process and what you are trying to do is possible with the help of automation. You can create a rule that will calculate the time difference between two status.

Take a look at this page for some examples on how to use smart values: https://support.atlassian.com/jira-software-cloud/docs/smart-values-date-and-time-functions/

I hope it helps.

Ravi

[Rui Caldeira]

Hi Ravi,

Will do, yes and thanks!

All I needed is something to trigger start counting down time from original estimate and that trigger could be the status change.

[Zoryana Bohutska _SaaSJet_]

Hi @Rui Caldeira 

Also, you can try SLA Time and Report(created by my team) It allows configure any issue field (including statuses) as start and stop conditions for time countdown.  

Regards

[Jack Brickey]

Hi @Rui Caldeira ,

how would you propose that this countdown timer be triggered on and off? I believe that for most users simply transitioning to say in progress does not mean that every second it is in that state I am actually working on it. 

[Rui Caldeira]

Hi Jack!

Well my idea is, if one sets Original estimate to say 2 weeks then the counter would start counting down till something like "0w 0d 0h". I do understand that I progress doesn't mean you're working on that specific issue all the time but then again, we have the original estimate and that for me means we can estimate how long it'll take till it gets done. 

Thanks for replying! :) I wasn't expecting an answer this quick.

[Jack Brickey]

But again how would this be triggered? I'm really just interested in how something like this might be implemented. Would the triggers be automatic or would it be something where you would simply provide a start stop button for the user. I recall from many years back there was a browser plug-in that would do just that but it really wasn't very useful in the end. I have seen some other post in the community along these lines but don't recall the details of the discussions. I do believe that there are add on like solutions out there for this so it may be worth scouring the community a bit to see if you can find a good solution it fits your needs. Cheers!

[Rui Caldeira]

What I've found online are pretty much paid plugins or code that people did and shared it online but that "original estimate" sounds to me like there could be something that would count that down... but I'll continue my online search and see what's out there. 

To answer your question: for me, the trigger would be automatic with the status change because I find it difficult for people in my teams to start logging or pause the counter by themselves. It's easier to just go through the tasks that are in Progress, by team member, and check the time left till the end of the original estimate. 

Thanks Jack!

[Bill Sheboy]

Hi @Rui Caldeira 

Adding to the thoughts from Jack and Ravi, I am unclear how this could help a team, even though it certainly could be done with automation rules.

Jira time tracking seems intended to help manage effort forecasts and working time, not the duration of work delivery (calendar time).  You note team members do not "pause" the counter, indicating people could be working on multiple things.  So logging work, or counting down from the original estimate, may not provide the useful information you expect.  That is, Work in Progress (WIP) could inflate the team's understanding of progress.

Instead, it may be better to track time for effort tracking and use the Due Date to assess time-to-desired-completion.

Kind regards,
Bill

[Jack Brickey]

yes well stated - effort vs. duration.

[Bill Sheboy]

Mike Cohn says it better than me in his agile planning info:

"Estimate Size; Derive Duration."