Thursday, March 4, 2010

An easy way to get more feedback: Shout!

User feedback is critical to making your application better. I absolutely crave feedback from users. However, it is probably also one of the trickiest things to accomplish. Feedback helps me guide new features and heavily informs upcoming versions.

My application, Worklog Assistant, just helps with JIRA time tracking. In the big picture, it's really quite boring to most people. So if it does the job, most people are content not to say anything. I thought that I should get more people to offer feedback, for better or worse. Maybe there are some obvious things I am missing (hint: there are!)

So, some time in January, I tweeted about an upcoming (very unscientific) experiment. At the time, I did not mention details to anyone. As you can guess, it had something to do with gathering more feedback.

At the top of Worklog Assistant's main screen, there are a few icons as seen below:

The little blue speech bubble has a tooltip which simply said "Send Feedback". Using Thunderbird's filtering capability, let's see how much feedback I got through this button over a seven month period:

That is a grand total of 8. E-i-g-h-t. Wow. According to Google Analytics, that is from a total of about 200 unique visits, for roughly 4% over all of 2009. I repeat: ALL OF 2009! Initially, I thought maybe no one cared (sniffle.) But then I sat back and thought about it from a user's perspective. Do I really want to "send feedback" for any apps that I use? The answer: ABSOLUTELY NOT!

Generally, I want to have a conversation with the authors of the application. And this has been my exact experience when talking to users. So I thought about it for a little bit. Eventually, I settled on changing the blue speech bubble to the following:

Why "Shout!"? I'd like to say this was based on some intuition but basically, I wanted something that people would click on which had some vague relation to its intended purpose and was enough to interest people. I released this change around the end of January and didn't really bother to check into it until a certain someone reminded me. Of course, I tweeted about the "experiment's" success!

Here are the cold hard statistics:

  • 170 unique visits to the target page in ONE MONTH due to this simple change. Compare this to 200 for the whole of 2009 and part of 2010.
  • Thunderbird says 12 new questions/suggestions as a result, a rate of 7%

The bottom line here seems to be that not only did I get more click-through, but the target page encouraged more people to initiate participation!

But there is another side effect. Some people that had never participated before now started to comment and vote on things they were interested in. So I think I've comfortably got a lower bound for new participation.

Conclusion

There is none. This is not a proper statistical test. But I think there is something there. What do you think?

Nitpicks and clarifications:

  • But this is not scientific! Yes, I know.
  • But you don't know whether it was the presence of the text or the value of the text which caused the greater traffic! Actually, yes I do (within the boundaries of being unscientific to begin with.) The first screenshot shown above was preceded by exactly the same icon but with "Send Feedback". Miserable, miserable click through.
  • But you could have had a 1000-fold increase in customers in that month! Oh, how I wish that were true.
  • But it could be because February is after January! Yes, you're 100% right. It could be.
  • But you said all of 2009 and 7 months! You liar! Well, I took a shortcut: The 7 months was the entire time the button was active so technically, I'm not lying.

Well I hope that was interesting for you. It certainly was interesting for me. Big thank you to "dermike" for reminding me to check into my experiment. You made my day.

Feel free to nitpick some more.


Sunday, January 31, 2010

Wanted: Brave souls for an experiment

I am in need of some brave souls who are willing to be part of a small experiment. I suspect most readers of this blog will meet the simple criteria I have for participants which is why I posted here.

The purpose of this experiment is to get an idea of what your work on the computer is like, in terms of context switches and away time. This will be represented in a simple graphical way which you may find useful even after the experiment. You can see an example at the bottom of this post.

All I would require from you is to let the application run in the background and send me a screenshot of the state of the application when you are done your work day. You can do this as often as you like but at least once at the end of your day is requested.

If you are interested, please email me and include:

  • Your primary job function (web developer, technical documentation, etc)
  • Your operating system
  • Whether you currently use JIRA or another project management tool

I look forward to hearing from you!

New release (1.0.1276)

A new release is available:

This release brings a couple of major bug fixes as well as some minor new features. The rest of this post discusses one of the new features. Your life may be made more complete by reading it.

JIRA's standard workflow is a little something like:

  1. Enter issue
  2. Assign to user
  3. User starts progress
  4. User tracks time against issue
  5. User resolves issue (progress implicitly stopped)
  6. Issue is verified and closed

If you're anything like me, you probably forget to do steps 3 and 4 regularly. Worklog Assistant helps you track your time in JIRA by being an interface you can go to to accomplish 80-90% of the work you need to do with your JIRA tickets. Indeed, if all it did was let you log your time worked, it probably would not be very helpful. Some of the things you can do from the Worklog Assistant interface:

  • Issue filtering and free text search
  • Workflow transitions (stop progress, resolve issue, etc)
  • Commenting on issues
  • Issue operations (edit, move, etc)

Typically, when you start tracking time against an issue, you are starting progress on the issue. However, JIRA has no mechanism that I know of (besides writing a server-side plugin) to perform the "Start Progress" transition when you log work.

So now, Worklog Assistant will helpfully execute the "Start Progress" transition the first time you log work against an issue. This means you never have to remember steps 3 and 4 again! One less thing to remember makes for happy people and happy people can only be good for your project.

With that, I bid you good day and hope this coming week sees you make a lot of progress!

Now, if only Worklog Assistant could do my work for me...


Sunday, January 3, 2010

New release (1.0.1135)

The first release of the new year is available:
This release includes some bug fixes and a new feature. See the release notes for details on the bug fixes.

Some users and myself noticed that a lot of the time, as soon as we turn off a timer, we published the worklogs to JIRA right away. So my workflow would be a lot like:
  • Start timer
  • Do some work
  • Stop timer
  • Command-P for publish (or CTRL-P on Windows/Linux)
Now you can click the "Automatically submit worklogs" option in the redesigned configuration window as shown below:

Whenever a worklog is added to the pending worklogs, it is automatically submitted. Any errors that occur are reported to you otherwise you can continue on your work. This is a good way to ensure that you don't forget to submit your worklogs to JIRA. As it turns out, this is a common occurrence. Hopefully this lets you work with a bit more security on that end of things.

Well, that's all for now! Have a good week and happy time tracking :)

Sunday, November 29, 2009

New release (1.0.1131) and x64 support for Linux

Note: I suggest everyone upgrade to this release if possible.

It finally happened. After attempting for as long as possible to have a single deb/tgz for 32 and 64-bit on Linux, I gave in and created a 64-bit package. The main reason for this was that Worklog Assistant now uses gnome-keyring to store passwords on Linux. As gnome-keyring is not part of the ia32-libs package, this meant a 64-bit package was needed.

If you install the PAM module, the keyring will be unlocked on login, otherwise the keyring software will prompt you to enter your keyring password when you launch Worklog Assistant.

So now, time tracking for JIRA just got a little bit better on Linux ;-)

There is also one bug fix due to the recent change to group worklogs by issue in the pending worklogs screen.

Thanks for your time and happy time tracking!

Sunday, November 15, 2009

New release (1.0.1128)

A new release is available. There are two major feature improvements in this release as well as official JIRA 4.0 support! The first being that pending worklogs are now grouped and summarized by issue. This should make it easier to see what you have worked on before submitting.

The next improvement is one of my favourites: on Mac, the dock icon now contains the total of all the pending worklogs as well as the current active task. See the screenshot below:

There are also some minor but useful improvements to the idle time detection. Previously, when you returned from idle, say to check email or the time, Worklog Assistant would pop up and ask you if you wanted to apply the away time to a task. This behaviour has not changed.

However, the dialog would previously assume that if you returned, you were back for good. Now, when you return, you can leave the dialog open and Worklog Assistant will continue to track your away time. When you finally return and accept, the correct away time will be used.

This is very useful for those cases where you are doing a software build, or a run of tests and just come back to check if they are done. From now on, you can just leave the notice open and your away time will continue to be tracked.

JIRA 4.0 support

Thanks to the awesome backward compatibility work by Atlassian, Worklog Assistant always maintained JIRA 4.0 support. However, I can finally say that JIRA 4.0 is now officially supported. This includes the server side plugin as well as the desktop client. As an aside, I have officially switched to using JIRA 4.0 internally and it is at least 100 times better than JIRA 4.0. My favourite "new" features:
  • Dashboard - Awesome!
  • Activity stream - What issue did I just change?
  • Greenhopper!
I used Greenhopper to manage this release and I must say I am never going back to the old way of bulk filter changes.

Last but not least, there is now a new "thin" installer for Linux. Basically, you untar+gunzip and you are ready to go. This should help on non-Ubuntu platforms.

I hope you find these new changes to be useful, I know I have. If you find any issues, please let me know.

Happy time tracking and have a good week!

Sunday, November 8, 2009

New beta available

It's been a while since a proper release but I'm coming around to it!

This beta has a bunch of minor improvements and one really cool new feature for Mac: a badge label for the Worklog Assistant application icon. Now, when you are tracking time and have pending worklogs to submit, the Worklog Assistant icon will show a label with the sum total of the elapsed time. Here is an example of what it looks like:

Pretty cool! Anyway, head on over to the beta site and give it a run, you'll be glad you did! Please let me know if you have any problems or suggestions.