[#JRA-1946] Automated time tracking

JIRA

Automated time tracking

Created: 07/Jul/03 01:35 AM Updated: 18/Jun/08 03:07 AM

Component/s:

Time Tracking

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue is duplicated by:

~~JRA-15107~~ Request for the ability to start, pause, continue and stop tasks and have this enter into work logs.

~~JRA-14907~~ Automatic Work logging.

~~JRA-3188~~ Would like option for JIRA to automatically time work done

Part

This issue incorporates:

JRA-9416 Create a workflow post-function to allow dynamic time tracking

Participants:	Anton Mazkovoi [Atlassian], Chris Bradshaw, Chris Wood, Dave Loeng [Atlassian], Jeff Turner [Atlassian], Nick Menere [Atlassian] and Peter Jang
Since last comment:	10 weeks, 5 days ago
Labels:

Description

« Hide

an automated work log feature would be great. If I start work on an issue, I'd click start and JIRA stops recording time for the previos issue (if any) and starts time trackking for the new one. I should be able to add a comment to the first / final / any time record and maybe adjust recorded times (in case I simply forgot to stop recoding before going home!) Since we are still a small team, we do have many interruptions and issue switches during a day.

– Kai Bounin

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Chris Wood - 27/Oct/04 02:02 AM

This would be a realy great feature.

A link from the top menu-bar to the 'current issue' would be neat.

Also, when beginning work on an issue it should be optionaly possible to change the assignee to the current user, or leave it as it is.

[ Permlink | « Hide ]

Peter Jang - 12/Jul/06 04:32 PM

When can i see this "feature" in the product?

[ Permlink | « Hide ]

Nick Menere [Atlassian] - 12/Jul/06 09:13 PM

Sorry Peter, this improvement has not been scheduled.

[ Permlink | « Hide ]

Jeff Turner [Atlassian] - 14/Jan/07 06:10 PM

The charting plugin has a "time in status" custom field, which could be used to expose the time each issue spent in the "In progress" state.

To actually use this info in a report of some kind is a much bigger task.

[ Permlink | « Hide ]

Chris Bradshaw - 04/Feb/08 09:42 AM

I am trying to get something around these lines by directly querying the database. What I have so far is...

SELECT 'CURRENT_STATE' STATE, p.pkey PROJECT, ji.pkey ID, to_clob(iss.pname) STATUS, (SYSDATE - osc.start_date) * 24 * 60 * 60 * 60 TIME_IN_STATE
FROM project p, jiraissue ji, issuestatus iss, os_currentstep osc
WHERE p.pkey='BIICDM'
AND p.id = ji.project
AND ji.issuestatus = iss.id
AND osc.entry_id = ji.workflow_id
AND ji.issuetype IN (SELECT id FROM ISSUETYPE WHERE pname = 'Incident')
UNION ALL
SELECT 'PREVIOUS_STATE' state, p.pkey PROJECT, ji.pkey ID, ci.oldstring STATUS, (osh.finish_date - osh.start_date) * 24 * 60 * 60 * 60 TIME_IN_STATUS
FROM project p, jiraissue ji, issuestatus iss, os_historystep osh, changeitem ci, changegroup cg, os_currentstep
WHERE p.pkey='BIICDM'
AND p.id = ji.project
AND ji.issuestatus = iss.id
AND osh.entry_id = ji.workflow_id
AND ji.issuetype IN (SELECT id FROM ISSUETYPE WHERE pname = 'Incident')
AND ji.id = cg.issueid
AND cg.id = ci.groupid
AND ji.issuestatus = iss.id
AND ci.field = ('status')
AND ((osh.finish_date - osh.start_date) * 24 * 60 * 60 * 60) < ((SYSDATE - osc.start_date) * 24 * 60 * 60 * 60 TIME_IN_STATE)
AND osh.finish_date is not null

However, Jira seems to create a new set of entries on the changeitem table for the status field every time the workflow is progressed.

This means you get the original entry of open to in progress, then on the next workflow step you get a new open to in progress and an additional in progress to on hold. Is this correct behaviour?

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 04/May/08 09:27 PM

While doing some housekeeping, I believe ~~JRA-3188~~ is a duplicate of this one. However, it goes into some more details about trying to prevent the automatic timer from recording erroneous time. I think it is relevant here:

It would be fantastic if JIRA would time work while an issue is being worked on (between pressing Start Progress and Stop Progress). It would have to "sleep" during off hours, which implies a working calendar (eg, M-F from 9 to 5), and users would need an "I'm on vacation" setting so that they could easily suspend work without having to Stop Progress on every issue. Ideally, developers could have personal calendars and an optional ability to overwrite the recorded work time could be available in a permission (so that an Administrator would have the ability to fix mistakes). This is something several of our developers have asked for and as a project manager, it's absolutely my #1 priority feature request.