Friday, August 31, 2012

Assignee Was!

AKA Saving yourself some serious heartache when it comes to logging hours...

So we all know logging hours is lame. I hate it, you probably hate it, and your Devs and QAs hate it even worse! One of the most frustrating parts is when you fall of the wagon for a bit and forget to log hours for an extended period of time. Well, JQL to the rescue! Tony Atkins of Atlassian calls it "Mining for Gold". JIRA 4.3 introduced the concept of  "Change History Searching", and the ability to search Assignee history was introduced in 4.4.

You have your choice of a bunch of different time period settings: After, Before, By, During, On and And. This leaves you open to do quite a few things:
  • Assignee was reese after -14d
  • Assignee was reese during ('2012/07/14', '2012/07/28')
    • Valid formats include: 'yyyy/MM/dd HH:mm', 'yyyy-MM-dd HH:mm', 'yyyy/MM/dd', 'yyyy-MM-dd', or a period format e.g. '-5d', '4w 2d'.
You may want add some limits in your query to filter out tickets you may not have actually worked on during that period, but were just sitting assigned to you:

  • Assignee was reese during ('2012/07/14', '2012/07/28') AND updated >= '2012/07/14'
  • Assignee was reese during ('2012/07/14', '2012/07/28') AND resolved > '2012/07/14'

No comments:

Post a Comment