Why we chose unfuddle..

Back in a previous life i used a customised version of bugzilla for bug tracking. It was fine, the UI was a bit basic but it worked fine. Then i started to notice how much time my manager was spending on its maintenance. Making sure the back ups were working, standing it back up when it went down etc.

At that point i kinda thought to myself that when i get into a position were i am choosing a bug tracker / project management solution to use i wanted one that i didn’t have to spend time maintaining. To cut a long story short that glorious day did arrive and i set to work looking just such a product.

In order to not suffer from the maintenance headache i decided a cloud based solution was in order. There is a wide selection of these so i ran a small project to get the development teams input, i wanted the whole team to buy into using such a solution and to buy into the winning contender.

I looked at these 4 solutions:

Screen Shot 2014-11-20 at 20.54.58

Screen Shot 2014-11-20 at 20.56.03

Screen Shot 2014-11-20 at 20.57.01

Screen Shot 2014-11-20 at 20.52.58

As you would expect each of these solutions had pros and cons but i had a wish list of features that we as a team thought we needed:

1. Had to be easy to use (We wanted no barriers that might stop colleges from all areas of the business using the tool)

2. Had to allow configuration of bug / new job status

3. Had to have a kanban style view (We use kanban and have a whiteboard that shows our jobs so we wanted our solution to allow us to view jobs in the same way)

4. Ability to create ticket reports easily

5. Have some project management functions

6. Allow unlimited users included in the monthly fee

7. Have GIT hosting.

How they shaped up

Along with the teams feedback and my own thoughts below is the summary of how the solutions shaped up:

1. Lighhouse had a very nice user interface but fell down due to its lack of project management features.

2. Bug Rocket was super easy to use but again did not have strong project management features.

3. Fogbugz was very feature rich both for bug / new feature tracking and in the project management area, downsides were that its user interface was rather old looking and somewhat difficult to use for a non technical user.

4. Unfuddle was easy to use, had a nice user interface, had adequate project management features and had that important kanban task board view. It also had built in GIT hub hosting, although at the time of writing this we have not yet migrated from our current GITHUB hosted repos. In short it hit all of the items on my wish list, rather than just some of them like the other solutions looked at.

To sum up unfuddle does a lot of things pretty well which suited us, you of course may have different needs so do a little project of our own to find out!

Let me know what your using an why in the comments!

Thanks for reading!