As a follow-up to my post about free hosted integrated solution for bugtracking and version-control, I’d like to introduce a great tool I accidentally found and then installed – Case Tracker.
It’s a free desktop application which allows you to easily view a list of current bugs, gives you a way to “start working” on the bug – so the time you actually spend on fixing the bug or implementing the feature is carefully calculated. So it’s basically a time-tracking application for a fogbugz – it takes the list of bugs
To start working, you need to enter your fogbugz username, password and the URL where you have it installed:
Case Tracker supports both FogBugz On-demand and hosted versions – it simulates all required POST requests as if you’re working with Fogbugz through your browser. As soon as you entered correct username and password, it will show you the list of active bugs:
However, by default it shows bugs assigned to anybody, which may be not always desirable. To address this issue, Case Tracker provides a search filter (funnel on the right-hand side of the pause button). For example, I need only those bugs that are assigned to me, so I add
assignedto:"Vitaly Sharovatov" as a search filter:
Then I press “Go” and get my list populated with only those bugs that I need! Awesome!
For more detailed instructions on the allowed syntax read this.
What’s really great in Case Tracker – it can automatically stop measuring time when you’re away from keyboard for a certain period of time:
However, Case Tracker doesn’t allow creating new cases – it opens your fogbugz URL in your default browser so you can enter new case there. But Case Tracker is not a replacement for Fogbugz UI – it’s goal is to simplify time tracking.
So the general flow is:
- you choose a bug from a drop-down list
- if the estimate hasn’t been set for this bug, Case Tracker prompts you to enter the estimate (using the same syntax rules as in Fogbugz in the browser)
- the work is started and time is measured – if you’re afk or just press pause button, it stops measuring the time
- when you’re finished – you commit the bug and mark it resolved either by specifying status:resolved in svn comments or using Case Tracker – I prefer to specify it in a submit comment – just got used to it.
So if you use fogbugz – this tool is definitely worth trying!