How to track time automagically?

[Mick C]

I would like to track time without the need for a developer to manually input start and stop times.

I can't see why this would be a problem but it seems to be that the only way to do this is by manually "clocking in" and "clocking out" when a task is updated across the workflow.

Please tell me I'm being an idiot.

[Aron Gombas _Midori_]

Michael, there is actually an add-on that makes it automatic, by starting and stopping the clock with status changes:

https://marketplace.atlassian.com/plugins/com.gebsun.plugins.jira.startwork/server/overview

[Mick C]

Thanks for that. I have started the free trial. I find it dissapointing that this very simple bit of functionality is going to cost me an extra $300 a year.

[Emily_Stubbs]

Michael - How is the $300 calculated? I'm trying to figure out how much this would cost for my company to implament.  
(Can't believe this is something we have to pay to add - How can time tracking be accurate if the 'amount of time spent' is just manually put in? That time could just be made up. ) 

[Mick C]

Hi Emily, sorry I have only just come back to this thread. The cost is worked out here

https://marketplace.atlassian.com/plugins/com.gebsun.plugins.jira.startwork/cloud/pricing

I have 70 Jira users, so at $0.55 per user per month

= $38.50 per month

= $462 per year

[David Willox]

Hi Michael,

I looked into this a while ago but the client decided there wasn't a need, so I've never actually implemented this but here are the links to get you started:

https://confluence.atlassian.com/adminjiracloud/configuring-time-tracking-818578858.html

https://confluence.atlassian.com/jiracoreserver073/logging-work-on-issues-861257349.html

Hope this helps.

Dave

[Mick C]

Hi  Dave, 

Thanks very much for the response but i dn't think it's quite what I'm after. 

I'm looking for Jira to lof the timestamps automatically, without a user having to do it. I feel like it should be simple and built in. but it doesn't appear to be.

For example

an issue transitions to "in progress" at X datetime, and moves to "done" at Y datetime. the length of time that ticket was worked on is simply Y minus X.

Thats  a simplification as there are many kinds of transition, but in essence it should be straight forward.