Hey all, a new release is available. Major changes:

• OSX dock icon: show timer status and elapsed time when running, unpublished time when timer not running
  
  
• Windows: show timer status in taskbar. Suggested by Ashley G.
  
  
• Fix for crash caused by infinite redirects
• Potential workaround for graphics-related crashes
• Better handling of "standard" issues

Download here: https://worklogassistant.com/download.html

Happy time tracking!

A new patch release is available. Just minor stuff:

• Avoid expanding worklogs on hover in timeline
• Enable automatic check for updates (OSX)
• Fix minor licensing issue

High DPI

Single sign-on support

Other changes/bug fixes

• Windows only: Allow minimizing/maximizing timer window from taskbar
• Fix log file naming
• Refresh timesheet automatically

Version 1.0.130817-r24dc is available. Sexy version number, eh?

• Download
• Release notes

Hello and welcome to another edition of "Stuff you didn't know you could do with Worklog Assistant."

As referenced in a previous post, custom scripts are a nifty way to extend Worklog Assistant to perform issue-specific housekeeping tasks.

For example, I use custom scripts to create and merge branches for a given issue. This is done through a "Context menu" script which allows me to add custom commands to any issue:



One of the recent additions to Worklog Assistant are a couple of new of "hooks" (in the Emacs parlance) or "extension points" (in Eclipse-speak).

The new hooks (can you guess what editor I use?) allow you to run a script when you toggle the timer on an issue and/or run a script once a minute.

People are already using them! Michael van Engelshoven was kind enough to share that he uses the new functionality to generate a git commit template:
With the output looking something like this:

• Custom scripts work by executing platform-native scripts
• Custom scripts are executed in response to different user interaction (none, explicit, implicit, etc)
• All properties of the current issue are exposed through environment variables. For example, the summary field of an issue is exposed as the variable JIRA_Summary
• Scripts that have a non-zero exit code are assumed to have failed and the user is notified.

Putting these together, we might guess as to how to prevent a user from tracking against an issue that is not a sub-task:

• Create an "Issue Timer Toggle" custom script (the name is horrible, sorry)
• Detect if the issue is a sub-task
• If not, the script should fail with an error message

No post is complete without a funny picture of a cat so here is a coder cat:

• Download
• Release notes

So it's that time of year again. New blog post! Don't you worry, releases have been occurring frequently even without blog posts. I have just gotten a little behind in updating the blog :)

The biggest change since the last blog post is JIRA 5 support. And the biggest implication from the user's perspective is that you no longer need any server-side plugin to access the "extra" data that we needed to before. Yay Atlassian! I'll be happy to retire that thorn-in-my-side at some point.

Besides that, a whole bunch of stability-related fixes have been included which should make Worklog Assistant run much longer and better for you. I not-so-infrequently get people emailing me telling me that they have left Worklog Assistant running for months! So to the few of you who have been having some problems (Mac users especially), you should be much happier. I couldn't have done it without the help of some very helpful customers who sent me log after log and tested build after build. Thank you! Here is a cat riding a bike for all your hard work:

In implementing the JIRA 5 support, I was able to clean up a lot of cruft and I am very happy with how things have turned out. I also brought in some code from v2 which was nice.

Check out the Atlassian Marketplace listing for Worklog Assistant. Leave a nice review for li'l ol me if you feel up to it :)

Happy time tracking!