Fogbugz - Great for all users and a large amount of projects
Use Cases and Deployment Scope
We used Fogbugz to manage books that our company was converting from paper to digital versions. For us, Fogbugz was a way to track not just bugs or software improvements, but projects and assignments that the team at large was working on. I oversaw a queue of book projects for five other workers, as well as running my own queue of fogbugz tasks and subtasks.
The case and subcase flow in Fogbugz works well if you want to visualize multi-step processes and how the processes are materializing. It was also good for users to self-refer to their tasks each day.
Pros
- Tasks, Subtasks, and notes. All three of these areas were critical for our team. Tasks in Fogbugz were a bit easier to see than in more bug based software like Trello or JIRA
- The entire screen is used to view a task or case. Clicking on a task or case will open up and take up the entire screen, aside from the sidebar nav columns. I like to see details and I think Fogbugz does this very well, using up as much digital real estate as possible.
- Flowcharting in Fogbugz with Creately is nice - instead of getting an exterior flowchart software like Lucidchart, Creately works right in Fogbugz.
Cons
- Personal dashboards could be a bit more customizable - i.e. if I log in, I'd like to see some of the cases more at the bottom of the screen and notes at the top. This is a minor minor quibble.
- I wish projects and cases within projects could be viewed in another format aside from list view. Perhaps a panel view or a card view would be good. That said, the list view is compact and agile.
Likelihood to Recommend
FogBugz is also good for tracking unanticipated tasks like bugs, making notes, flowcharts, and categorizing if the problem is a bug, feature request, etc. For us, it was just the best at nailing down those anticipated tasks.
