FogBugz vs GitHub: What are the differences?
Developers describe FogBugz as "The world's easiest bug tracking system". FogBugz tracks bugs, issues, and customer support tickets through every stage of the development process. We built it to be quick and easy to use, so that your developers will actually use it. Over 20,000 teams from the world's best software companies use FogBugz because it keeps their developers productive and happy. On the other hand, GitHub is detailed as "Powerful collaboration, review, and code management for open source and private development projects". GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.
FogBugz can be classified as a tool in the "Issue Tracking" category, while GitHub is grouped under "Code Collaboration & Version Control".
Some of the features offered by FogBugz are:
- Issue and Bug Tracking- Effortless Bug Reporting, Customizable Case Lists, and Full Case Histories
- Project Management- Wikis, Evidence-based Scheduling, Task Outlining, and Reporting
- Customer Support- Email Management, AutoSort, and Snippets
On the other hand, GitHub provides the following key features:
- Command Instructions
- Source Browser
- Git Powered Wikis
Airbnb, Netflix, and Medium are some of the popular companies that use GitHub, whereas FogBugz is used by ebay, PayPal, and Foursquare. GitHub has a broader approval, being mentioned in 4714 company stacks & 6099 developers stacks; compared to FogBugz, which is listed in 11 company stacks and 5 developer stacks.
What is FogBugz?
What is GitHub?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose FogBugz?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using FogBugz?
Sign up to add, upvote and see more consMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
For starters you can fork a repo, edit it online and send a pull request which is huge if its something very small that you want to commit. The whole pull request system, the UI and the UX are great. If I sent out a pull request that failed on travis CI then all I need to do is fix it in my fork and the original pull request will have these updates as well making it super easy for everyone involved. Overall a great service.
I love GitHub! They provide a completely free service for hosting, storing, and collaborating on code. Seriously, if you aren't using them, go sign up now.
Great collaboration-friendly git repository hosting. Plus integration with all sorts of other stuff, like Travis CI. But the command bar has disappeared...
It's the best tools I have ever used.
"Having a CI server building all commits across all branches was a huge first step, but to make this useful we needed to surface the outcome of these builds. This is where GitHub’s commit status API comes in. Every time our CI server begins a build, it pings GitHub’s commit status endpoint, and every time it completes a build it hits the endpoint again with the outcome. Now every open PR includes a yellow/red/green indicator for the branch in question, with a direct link to the build status page on our CI server. In practice this means more transparency, faster feedback cycles, and a guarantee that every branch merged into master has a passing test suite. This integration has been a huge help in keeping our master branch green, and has thus greatly reduced our deploy times (since engineers aren’t waiting on build failures to be resolved in master)."
Pervasive, easy to use Git repo hosting. I host ongoing personal projects privately and my personal blog (via GitHub Pages).
I also take successful proofs of concept (for example, experimenting with linking AWS Lambda to Heroku Postgres to create a serverless SQL backed web app), and host them as public example repos. These are linked to Dependabot and CircleCI if they have tests so that dependencies can be kept up to date automatically over time and the code using the dependencies can stay fresh over time for example viewers.
GitHub is a Web-based Git version control repository hosting service. It is mostly used for computer code. It offers all of the distributed version control and source code management (SCM) functionality of Git as well as adding its own features. It provides access control and several collaboration features such as bug tracking, feature requests, task management, and wikis for every project
Yeah, so we use GitHub, and we basically use a variant of continuous deployment where when anyone merges in a feature that they’ve finished with, they ship it immediately, and we bundle it up as a build pack and send it to all of our EC2 servers... Any developer on the team can trigger a build and deploy at any time. So on a given day, we probably deploy 20 or 30 times to prod.
One thing I really wish GitHub had: Trello-style kanban for Issues. There are a bunch of services and tools that add Kanban to GitHub Issues. But Trello just seems far better. If GitHub had it’s own kanban tool, I’d probably use it. Right now it’s pretty painful to try to tie cards to commits manually (when/if we remember to).