Time tracking

We use Kimai for our time tracking. All employees, irrespective of their roles, need to track their time effectively. This guide will outline how to write clear, consistent, and meaningful time tracking descriptions.

Granularity

In Kimai, log Duration to the exact minute by using a supported format. You can accomplish this by selecting + Create or using the play button to add a new record.

More detailed information can be found in the Kimai user manual.

How to write descriptions

Use action verbs

Start your descriptions with action verbs such as 'develop', 'design', 'fix', 'review', etc.

Include relevant issue or pull request IDs

When working on specific tasks, include relevant repository names and PR or issue IDs in your time tracking descriptions by copying the path in the URL. This facilitates cross-referencing with project management tools.

✅ Good

"[wallops/console/pulls/6]: Update region test data"

🚫 Bad

"[PR#123]: Work on PR"

Be specific

When writing descriptions for time tracking, be as specific as possible. Avoid vague descriptions. Instead, describe precisely what tasks you have worked on or completed.

✅ Good

"[wallops/console/issues/2]: Write copy for the about us section on our company website"

🚫 Bad

"Work on the company website"

Consistency is key

Ensure consistency in your descriptions. Consistent formatting helps in tracking progress and analyzing data later. Decide on a format and stick to it throughout the project.

Avoid jargon

Keep descriptions simple and avoid jargon. If jargon must be used, ensure it's universally understood within your team.

Regular updates

Don't let too much time pass between when you worked on the task and when you track it. The fresher the task is in your memory, the more accurate your description will be.