When comparing Taiga vs Pivotal Tracker, the Slant community recommends Taiga for most people. In the question“What are the best project management tools?” Taiga is ranked 14th while Pivotal Tracker is ranked 20th. The most important reason people chose Taiga is:
User stories can be organized in both Kanban and Scrum task management systems.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Supports both Kanban and Scrum modes
User stories can be organized in both Kanban and Scrum task management systems.
Pro Free and open source
Taiga is licensed under GPL with source code available on GitHub.
Pro Simple to use
Pro Comprehensive Agile software development toolset
Taiga tries offering a complete Agile software development toolset. It includes complete solutions for issue tracking, videoconferencing, documentation (in the form of a wiki) and either a backlog or a Kanban board for managing user stories.
Pro Built-in issue tracking
Taiga has built-in issue tracking tools. The issues can be organized by user-defined type, severity, priority, creation date, assignee, creator, tags as well as filtered by subject. Taiga can also integrate with GitHub, GitLab and BitBucket.
Pro Built-in wiki
Each project has a wiki. It has Markdown support as well as a WYSIWYG editor.
Pro Built-in video conferencing tools
Integrates with either AppearIn or Talky to provide a video conferencing solution.
Pro Migration from RedMine
Pro Export/Import feature
You can extract all your data from one Taiga instance and move it to another one. You can read more here.
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).
Cons
Con No Kanban metrics
Taiga is said to support Kanban but it does not generate any of the usual Kanban metrics (cycle time, lead time) or graph (Cumulated Flow Diagram).
Con Can be overwhelming at first
Taiga presents users with a lot of information and functionality right from the beginning with little guidance. Figuring how stuff works might take a bit.
Con Too much functionality for small projects
While it's possible to disable any unwanted features (modules), the amount of functionality that's present might be more than a small, short-term project needs.

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.
