We love receiving feedback and suggestions via our people powered forums, and 99% of the time these cover important points which we resolve as soon as possible in order to maintain high levels of customer service.
It`s a rare thing, but there have been times in the past where suggestions have been made for features that are already present within fixx, similar to the insights I shared in my previous post. In this post I am going to share another of these with you.
A great example is the results of a filter, unless specified, these can return a list of any matching issues spanning over a number of projects. The way they are presented currently, shows various issue attributes such as its ID, Priority, status, Type, Title and who it`s Assigned to.
One suggestion was to add more columns to the filtered list of results which would present more meta-data to the current user, such as the Project it falls under, when the issue was created and when it`s due to be completed by.
This is a very valid point, and we took this into consideration whilst designing fixx, and we came to the conclusion that the information which is currently onscreen is the most important and fitted the workflows we created during the design phase.
To make sure people don`t go without, we also implemented a hover activated Quick Information box over each Issue ID which displays the remaining issue attributes as can be seen in the screenshot below. To show the Quick Information box, all you need to do is hover your mouse over the issue ID for a couple of seconds.
I`m betting that a lot of you were not aware of this feature at all. There are a few more of these posts on the way, so make sure to watch this space for more great tips.
Yesterday, Sarat and I were doing some pair programming on our new but shockingly large 37" LCD TV that's on the wall in our fancy meeting space in the lab.
Pair programming is fun and you learn a hell of a lot! If you want to know more about why this is the case, I suggest you read this great article by Obie Fernandez.
We were ironing out some bugs for the fixx 1.7 release, and I had a filter set-up to give me all the issues that had to be resolved for that particular release. As a result I was jumping back and forth from the filtered list of issues, to the full view of the issue we were currently working on.
It was in this process that Sarat made, what seemed to be an odd observation at the time; that I was doing things wrong. I couldn't understand how, as fixx is made to be simple. I went back to the Dashboard and proceeded to click on my "fixx 1.7" filter to go back to the list of issues we were working on.
Sarat then noted "You do realise you could have got back to that list by pressing the Issues tab, rather than navigating back to the Dashboard and invoking your filter...right?".
Obviously I was not aware of this, and feverishly tried it out to find out he was right. Of course he's right; he wrote it!
fixx remembers your last used filter no matter where you go in fixx, and when you return back to the Issues tab presents the list of issues from the last filter. Even if you apply a temporary filter without saving it, the results of that filter are remembered in your session, and can be viewed once again when you return to the Issues tab.
It's evident that I was in need of this piece of functionality, as issue tracking should not by obtrusive by any means, and it turned out to be there all along but I just wasn't aware of it being the new guy in the lab HQ. You can tell that a lot of thought gone into the design and functionality in fixx, and the more I think about it, the more it makes complete sense. As a result this is one gem I want to share.
You're either going to read this and think, how on earth did he not know that, or you're going to go away and try it out for yourself and increase your productivity. Either way I'm happier that I am now aware of this, and hope that it manages to have an impact on the way a few of you use fixx.
