Likelihood to Recommend 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.
Read full review If you are familiar with IBM Rational Suite products, RequisitePro will add up due to the synergy between other components. Beyond that, if your business is not structured to an adequate development methodology or lacks the degree of maturity or necessary resources, probably RequisitePro does not add much value. If you work with developers in the requirements analysis, they probably prefer to use an SVN repository.
Read full review 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. Read full review Capability to query bugs on multiple criteria and export it to csv for triages. Simple and intuitive user experience and clearly planned defect life cycle There are other features like assigning the defect to pull request, clearly explaining defect by attaching screenshots, detailed description etc If you are using other IBM tools for requirements documentation, this tool integrates very well Read full review Cons 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. Read full review Performance can be an issue. Make certain the server is sized properly There is a large difference in capability of the Thick Client Version compared with the web based version. Make certain each job function has proper access to be able to do what is required of them. Learning curve is not too steep, but would suggest having someone with experience setup the repository. Highly suggest getting a contractor to assist to get the repository up and running. Read full review Likelihood to Renew Most likely as it's one of the powerful tools in the organization. We needed this tool to track all the process related documentation and also to capture signatures.
Read full review Usability Please keep in mind that this all has to do with you you customize the user interface. It becomes very easy to house all of your requirements, but it may and can make life difficult for you if you do not think ahead of how you want the app to work and house your data
Read full review Support Rating IBM has good support and knowledge base. With the wealth of information on their site and the support desk, we were able to quickly resolve issues. It is smart to build up a COE and a group that manages the software otherwise it is quick to be able to lose the knowledge as team members are assigned different duties
Read full review Implementation Rating It was pretty simple.
Read full review Alternatives Considered I like
JIRA a lot better than Fogbugz for many reasons. If I had a choice, I'd use
JIRA every time
Read full review IBM clearquest would the BEST option if you are looking for managing change requests, managing project workflows, generating reports on status of requests. The reason being: cost, cost and cost. It almost handles everything that you would need for your project including bug tracking unless you want something really fancy (like HP QC) with a higher cost that supports a wide variety of needs which you might need to evaluate based on your project needs. For example, if you would be really making use of all those additional features provided by HP
Quality Center . To be honest it depends on your project size, the skills of team members and of course budget!
Read full review Return on Investment 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 Read full review IBM Rational ClearQuest has provided a workflow that works without unique software methodology. As a result we deliver complete software products to our clients in a 6 to 8 week development time frame. As a result of our highly customized implementation, we have 8 resources supporting IBM Rational ClearQuest. Three of the resources are full time configuration management staff that administer and support the tool set and the other 5 are from the testing group that handle ClearQuest user support issues in addition to their testing duties. Read full review ScreenShots