FogBugz vs. Instabug

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.

Incentivized

Instabug is great to capture bug reports during the testing phase of your app. You can also collect user data such as device, OS, and App version to easily reproduce the issue.

Incentivized

• Good for documenting
• Good for attaching things

Incentivized

• Instabug allows testers to quickly and easily send their bug reports.
• Testers can draw on the screenshots, capture video and write back.
• Instabug also has amazing customer support that is always quick to respond to our requests and needs.
• Users can also make integrations so you can easily turn Instabug reports into Jira or other tracking software.

Incentivized

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

Incentivized

• Could be less pricey.
• Should be something that works not just on IOS and Android but also on web applications.

Incentivized

FogBugz is made for the Developers who actually use it every day, while JIRA is made for the C-Suite who oversees them but has little idea of the finer points of daily dev tasks. In reality, most don't fit into the mold of JIRA tickets, and the summarized information that C-Suite is reviewing is incomplete or skewed. There is also an outstanding issue since 2004 that JIRA refuses to implement despite wide user support, the merging of tickets. You can see the open ticket with the JIRA team here: https://jira.atlassian.com/browse/JRACLOUD-3592

Incentivized

• Less downtime of jobs. It is each person's responsibility to check their list to see if they have any pending work.
• When people are out sick or busy, a supervisor can easily shift work from one person to another who many have time to cover work.
• Management has a quick view into seeing what is happening with a job and can use it as a tool to request addiional resources as needed.

• Reduced the time to get feedback.

Incentivized