BugSnag vs. FogBugz

It's great for tracking bugs on your app. I don't think I can do anything else besides that...

Incentivized

FogBugz has been a very useful tool to our organization, and much preferred over other options we reviewed, mainly JIRA. There are still some improvements needed, but with the fairly recent acquisition by DevFactory, we have a great deal of hope for what is in store given DevFactory's focus and transparency. It seems like both DevFactory and FogBugz customers are eager for substantial improvements on the front-end, but there is/was a great deal of backend housecleaning that definitely needed to take place first.

Incentivized

• The UI/UX is well designed. I have never been confused by any buttons/filters/settings, and everything is laid out in a neat and organized fashion.
• Setup was super easy. I didn't have to do anything but read the documentation, which was well written.
• The information captured by errors has everything I would need to debug an issue.

Incentivized

• 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.

Incentivized

• For really long bugs, it'd be nice if you hovered over the row and it expanded the text so you didn't have to click on the actual bug to view everything.
• It would be nice if there was a filter for grouping bugs instead of searching by their name.
• Honestly nothing else, I love 99% of Bugsnag.

Incentivized

• The simplicity of a single admin type user is not great because anyone who can create a job or client in the system, can also add and delete users. Content and User administrative rights should be separated.
• There are ways to change the terminology/lexicon within the tool, but we are not able to get it to work even after reaching out to tech support. So we are forced to use the system terminology that doesn't match up to our company making training a bit difficult.
• There is a subscribe function that you can opt into, there should be a way to add subscribers as you create a new task.

I like JIRA a lot better than Fogbugz for many reasons. If I had a choice, I'd use JIRA every time

Incentivized

• It has caught bugs on the spot, which allows us to quickly fix them.

Incentivized

• Saves time by quickly allowing Developers to make the necessary notes without getting bogged down in bloated UIs
• Has allowed us to look back easily and see the exact code changes made for the exact Case to aid in decisions for current changes, increasing the certainty of the decided path, without regression

Incentivized