Some Time Tracking Updates

For those of you who have time tracking enabled on your projects, we have just rolled out a number of changes to time tracking.

Powerful Commit Messages

We have added a few time tracking related actions to our Powerful Commit Messages. It is now possible to specify how many hours you have spent on a ticket using the following syntax:

  > svn commit -m 'spent 5.5 hours on #498'
  > svn commit -m 'resolved #47 spending 2:45 on #47'
  > git commit -am 'worked 3 hours on #99'

The keywords that will trigger the creation of a time entry are: spend, spent, spending, invest, invested, investing, work, worked, working.

Please note that the ticket number must always be specified in association with one of the above keywords and they must always be separated by either the word "on" or "hours on" (i.e. "5:30 on #43" or "5.5 hours on #43").

Time Entry on Ticket Resolution

When resolving a ticket, it is often necessary to create a time entry representing the work you put in to close the ticket. Previously, this was a 2-step process. Now, you can simply specify the amount of time spent resolving a ticket right from the ticket resolution form.

Time Entry on Ticket Resolution

Additionally, as you may have noticed from above, it is now possible to use a more natural ":" separated notation everywhere you enter hours. For instance, instead of having to write 10 minutes as "0.1666", it is now possible to simply write "0:10".

  1. October 8, 2009 Zupo

    Great! Love the update!

    Keep up the good work!

  2. October 8, 2009 Brian Kemp

    I was just remarking to myself yesterday about how the two-step time entry process was a little silly. I'm glad you saw it too and gave us another option for time entry.

    My project doesn't require time entry but I put it in as habit.

  3. October 9, 2009 Richard Bailey

    Good updates, but what I really want is to see my time such that I can assign time to tickets by clock time and not by hours. Eg. 9am to 10am. I want to be able to see my day and where my unaccounted gaps are, and where abouts on the clock my team are claiming their hours.

  4. October 9, 2009 ShayneM

    Excellent news, I am genuinely happy to see Unfuddle moving forward and responding to users requests - min included :-)

  5. October 13, 2009 Erik Hansen

    This is great. Most of our team uses for tracking, but for those that don't, I'm sure this will be useful.

  6. October 14, 2009 Rob Levin

    OMG, that rocks! Good job guys ;-)

  7. October 22, 2009 Simon Hamilton

    This is a great feature, but there is one big problem for me. When running Time Tracking reports, the messages just say "Changeset [myproject:95]", which means I have to go fetching the changeset messages and pull it together to provide reports to our customers. What would also be useful is per project Time tracking reports.

  8. October 28, 2009 Eric Marden

    Great changes, all. However, the default messages of the automated time logs make the reports useless.