CRO Ticket Time Tracking

Purpose - to log the time elapsed on each request.

Goal - to help analyze how we are allocating our time, which types of tickets are taking up most of our work hours, and to generate time tracking reports for overview.

Required Steps - once you pick up a ticket and the ticket status is “In Progress“, please click on the top right corner drop down menu and click on the “log work“ button:

Open

On the popup window, the only mandatory field that needs to be filled in is the “Time Spent“ field, with however many hours, days or weeks spent working on this task.
For instance, if I picked up a split test ticket, before I finish off my ticket and mark it as “Done“, I would click on log work, and note down the hours I spent on this. Please note if you are finishing the ticket on the same day that you’ve started on it, you don’t need to adjust the Date Started field.

Example of Process:

• After picking up a split test idea, log in the time spent making all the design/copy/dev tickets

• Account for the time that the test is up (if the test was up for 1 week, log 1w in the window)

• Account for the time for the report

Open

Ideally, when each ticket is closed, you should see the time logged section pop up on the right hand side of the ticket, noting down the hours spent on this ticket. And at any point an time, you can click on the “+“ icon towards the right of “Time Tracking“, to change the hours logged.

For Tim:

At any time, if you want to access the summary of everyone’s work logged, click on “Team Reports“ from the left navigation bar.
From here, you can select the time period, project, user(assignee) and jql filter. For instance, if you want to check how long we’ve spent on blaux split tests, in the jql filter field, type in “epic = blaux“, as long as everyone labelled their tickets correctly, this will populate correctly.