When comparing Pivotal Tracker vs Bugsnag, the Slant community recommends Bugsnag for most people. In the question“What are the best free bug-tracking tools for programming? ” Bugsnag is ranked 12th while Pivotal Tracker is ranked 30th. The most important reason people chose Bugsnag is:
Clear, concise documentation. Plus [docs on cross-domain script errors and enabling CORS](https://bugsnag.com/blog/script-error).
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Flexible
While not perfect kanban, Pivotal is somewhat flexible in that you can mark sections of stories. So rather than (or in addition to) a normal sprint, you can put a marker in to define all cards above that point as part of something, for example a release. Further, you can override the auto tracker and define how many points in a sprint. So there is some degree of flexibility which sometimes you don’t find in “purist” agile or scrum tools.
Pro Great software to use in conjunction with a disciplined agile/scrum development philosophy
Pivotal Tracker has a Kanban feel to it, but takes a more opinionated “Agile” approach to feature management: It encourages items in the flow to be user stories with effort points associated to them to allow Pivotal to calculate your team’s velocity.
If you agree with the workflow, Pivotal offers a ton of functionality not provided by more generic tools like Trello. You can see your team’s velocity over time, organic smaller Stories into “Epics” (huge features) etc.
Pro Stories can contain media files
Easy to create features/bugs/chores with embedded files (screenshots, docs, videos).

Pro Great documentation
Clear, concise documentation. Plus docs on cross-domain script errors and enabling CORS.
Pro Email, chat, sms notifications
Bugsnag can be set up to send email notifications as soon as exceptions occur. It can also integrate with a number of third-party services that can be used for notifications including Campfire, HipChat, Twilio SMS and custom solutions via Webhook.
Pro Automatic issues/ticket creation
Bugsnag integrates with a wide variety of 3rd party tools to automatically create issues or tickets. Integrations include GitHub, BitBucket, UserVoice, Trello and many, many others.

Pro Has a free plan
After a two-week full-featured free trial period the user is limited to 2,000 errors/month, 1 user and 1 project.
Pro Exceptions are grouped
Bugsnag groups similar exceptions together displaying the number of occurences so that there's no need to deal with each instance of the error separately.
Pro Exceptional documentation organization
Their documentation was well organized, easy to search through for the platform of choice and quick work of full product integration.
Pro Supports Unity 3D
Drop in place integration with Unity 3D, only a simple API Token configuration on game object and everything was up & running with almost zero code written.
Pro Supports phabricator integrations
Not many products have decided to finally start doing this, phabricator now has a champion.

Pro Source map support

Pro Stack traces
Pro Client libraries are open source

Pro Report uncaught errors
Pro Good web UI
Cons

Con No Kanban-board
To get a good overview often Kanban boards are used. You can somehow imitate a board, but it is not comparable to a real Kanban-board.
Con Limited Work Flow & Process
Few story states. If your process involves some sort of QA and sign off, forget it - you get started, deliver, accept/reject, and finished. No way to customize this to your process. Sad miss for an easy fix/configuration.
Con Non-Editable Default Templates
Templates for defining stories and bugs save time. Pivotal has a default for story and bug. However you can’t edit these. So when you go to add your own, the titles can be confusing to users. Maybe title like “Our User Story” and “Our Bug”? Users will see all templates in the drop down and it’s confusing, so you end up with peope using the wrong templates which adds to process problems.
Con No Saved & Shared Views
Everything is in a column. Aside from destroying Kanban, it also gets confusing. The real downside here is that there’s no way to save a set of columns and pin for others to quickly see. Everyone on the team is usually looking at a completely different set of work. This is literally the definition of not being on the same page.

Con Not usable for multiple projects
If you want / need to have an overview of all the tasks going on over different projects and if you have these organized in different projects, there is no way to get an overview beside reporting. Just take a look at the screenshot and you see what you can expect.
Con The tool seems flaky
De-obfuscation doesn't always work on react-native projects.

Con Blocked by ad blockers by default
Bugsnag is blocked by the AdBlock EasyPrivacy filter.
