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: