BugTracker.net vs. FogBugz

See above. Recommended questions: What type of feedback or tracking will we be doing? Will this need to be client-facing? How will we track content edits? How many users will be assigned to issues in a given project?

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

• Ability to split our multiple projects and assign a user base.
• Ability to set permissions based on user base/ roles.
• Customization of fields on a project level.

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

• User interface for client-facing feedback
• Content and design updates tracking

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 would plan on renewing and staying with BugTracker.net simply because it is a no nonsense easy to use tool. Once you get it set up and understand the small nuances with this custom piece of software, it really is a great tool to help your organization get started with Defect Management and BugTracking without having to drop several thousands of dollars on tools that are more fluff than function.

Incentivized

I didn't choose the product or evaluate other options, but I've been satisified with it except for tracking content changes.

Incentivized

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

Incentivized

• Decreased turn around time for defect fixes.
• Smoother builder deploys
• Clearer communication from QA to Dev Team

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