Best practices for time logging

[Ian Bussieres]

Our team is running a sprint on greenhopper to see how we like the tool. So far, I have to say we are quite happy with it. There is, however, one regard we still want to address.

On our past tool, we would log time against different activities. For example, a developer could log day 1 something like this :

Development 4h

Meetings 1h

Testing 30m

Analysis 2h

This would allow advanced reports of how the team might of lost time on meetings, or how the team could be more efficient on different phases of the lifecycle (ex: deploying). We would also speratly track such things as experimental development or research for different tax credits.

I have not yet managed to find a way to accomplish anything similar... any hints ?

[Jobin Kuruvilla [Adaptavist] · Accepted solution]

You should be able to use JIRA's time tracking for this.

https://confluence.atlassian.com/display/JIRA/Configuring+Time+Tracking

[Jobin Kuruvilla [Adaptavist]]

Also see https://confluence.atlassian.com/display/GH/Sprint+Hour+Burndown+Charts

[Jobin Kuruvilla [Adaptavist]]

Ah I see! It is not possible out of the box in JIRA. You might be able to use some plugins like the Tempo plugin to have categories.

[Ian Bussieres]

Yep. Those two options I knew of, but neither does what I'm asking for. I really wish to have an additional parameter for logging time. See it as a a time 'category'... I need to be able to specify what 'category' of work was logged.

[Steffen Stamprath]

Hi Ian,

the easiest way to track time it the Plugin "Meeting Time for JIRA". It helps to log time only for one user, for meetings with multiple users.

https://marketplace.atlassian.com/plugins/aptis.plugins.meetingTime/

Best regards
Steffen