Taiga vs JIRA Agile
When comparing Taiga vs JIRA Agile, the Slant community recommends Taiga for most people. In the question“What are the best online Kanban tools?” Taiga is ranked 1st while JIRA Agile is ranked 11th. 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 Highly customisable and powerful workflows
You can provide custom workflows for all the different types of issues. For example you can make features go through a flow of "Backlog -> Needs design -> Built -> Needs QA -> done" with bugs going through a different flow. These workflows are very powerful as you can configure them to automatically assign your QA lead when moved into the needs QA state. These features do require some learning curve to set up, but make the tool a lot more efficient to use as things like managing who is assigned to an issue can be automated.
Pro Powerful tools for issue management
Issues in a current sprint are viewed in a Kanban interface. But for the issues not in a sprint Jira provides a compact view with many powerful tools to search and filter the list. You can create custom filters such as "Show me all issues not yet designed that are assigned to me" and a variety of other tools that make dealing with large backlogs easy.
Pro Has App Marketplace for extensions
Pro Helps you focus on what's important
Jira is a truly Agile software as you may concentrate on the active sprint and the tasks you have to do.
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 Slow to use
Every view switch and action takes a second or two. Doesn't seem too bad when you first start using it, but the UI is complicated enough that you need to manipulate it a lot and all that time adds up.
Con Merely a thin interface to a massive database
Too many configuration details, too confusing, too difficult to search and modify numerous tickets.
Con Email defaults are crazy-bad
The default is seemingly to email everyone on the team every change on every ticket. Which is stupid-bad. It means you get spammed with so much JIRA garbage you miss actual message tagged with your name.
Con Terrible editors barely work
The in-page editor for issues have lots of issues, plus several hacked-together features that barely work with each other. It's nice that you can drag and drop an image, but just try to format inline text as code, or block text as code, or to use the styles, and you'll find several places where things just FAIL.
Con Expensive
User based price model
Con Ancient
Non-reactive interface.
