About TrustRadius Scoring
Score 2.6 out of 100


Recent Reviews

Read all reviews
Return to navigation


View all pricing

3 Years


per month

2 years


per month

1 Year


per month

Entry-level set up fee?

  • No setup fee


  • Free Trial
  • Free/Freemium Version
  • Premium Consulting / Integration Services
Return to navigation

Product Demos

A Quick Introduction to FogBugz
Return to navigation

Product Details

What is FogBugz?

FogBugz Video

A Quick Introduction to FogBugz

FogBugz Integrations

FogBugz Technical Details

Deployment TypesSoftware as a Service (SaaS), Cloud, or Web-Based
Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation


View all alternatives
Return to navigation

Reviews and Ratings



(1-4 of 4)
Companies can't remove reviews or game the system. Here's why
Score 7 out of 10
Vetted Review
Verified User
FogBugz is used primarily by our Software Development Team for Issue Tracking, Source Control, and Wiki. Our Support Team will create Cases for Dev to look into, as they need more feature rich services for Customer Support. The entire company will reference the Wiki for internal documentation. We also have a public Wiki which serves as a place for us to post information/steps to our customers.
  • Evidence Based Estimates for scheduling (This alleviates issues that arise due to people who estimate time poorly)
  • Made from the developer perspective, versus others that are by C-Suite who are so far removed from the actual development process they just contribute to the disconnect or inaccuracy of the system
  • Direction/Ambition/Transparency of DevFactory after their purchase of FogBugz/Kiln is refreshing
  • Workflow capability is very limited to the original implementation, could use a refresh and extension of the capabilities
  • UI/UX needs improvement. This was in the works prior to purchase by DevFactory, and has taken a back seat to backend improvements that rightfully needed to be fixed first.
  • Pricing model doesn't fit our usage very well, so we're paying for full-featured users for everyone even though the majority of Users only need to submit Cases and modify the Wikis, and our small percentage of Users are in Dev and need all features.
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.
Becky Jewell Laughton | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

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.
  • 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.
  • 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.
Fogbugz is great for case-and-task based businesses. If your business has hundreds of weekly anticipated tasks that exist, such as processes to get files converted, Fogbugz can manage these processes very well. For our team, we knew each week that we would have about 500 tasks or orders to get processed. Fogbugz helped us break down these projects, get them assigned evenly throughout the team, and easily see who is working on what task.

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.
March 29, 2017


Gillian Hughes | TrustRadius Reviewer
Score 3 out of 10
Vetted Review
Verified User
Use to track bugs that were found in projects. Used to track the fixing of bugs found during testing. Used to communicate the specs of new projects and to answer questions asked by business owners and QA. Used across whole organization. Addresses teh business problems of communicating with different employees across different time zones and countries.
  • Good for documenting
  • Good for attaching things
  • Missing keyboard shortcuts
  • Missing a good way to link external documenations
Fogbugz is ok. It's good for bare bones bugs and projects, but lacks the functionality of JIRA. I hate not having shortcuts. I don't like the way the cases are laid out. I don't like the search. I don't really like much about it. It's very simple and bare bones, and just not enough for me.
Ted Shimizu | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
We are currently using Fogbugz for our internal Production, Development, and Project Management teams. It is serves as a light weight task management system to move/track jobs between departments. it is effectively a virtual job jacket for our creative agency. We introduced the tool to support our teams with tracking fast moving jobs and keeping individuals accountable for responsibilities for a given job. It also helps team member transitions and coverage by showing a quick summary of the job history.
We selected the tool for it's simplicity, flexibility and ease of management because it would be used company wide accommodating varying experience levels of task management literacy.

  • Simplicity: Compared to other tools like Jira and even Bugzilla, Fogbugz minimizes the number of fields. The general workflow and status' of a given task works well for us. (Assigned, Resolved, and Closed).
  • Flexibility: The list views are highly customizable. This allows for many ways to display information and create custom lists for teams and departments. It has prebuilt queries, and basic boolean syntax that you can stitch together to build a list.
  • Easy to maintain: There are just two types of access rights. Regular and Admin. With some training, administration of the tool is done by project managers and a general user admin. We have a self hosted version, so there is an IT component in our maintenance, but it does not requires much attention.
  • 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.
Do you have trouble keeping track of work in progress?
Do your jobs jump around alot and often sit idle?
Are there process bottlenecks where better access to job/task transparency will help move a job along better?
Are there common issues related to coverage and you find yourself digging through emails to figure out job status?
Return to navigation