When comparing JIRA Agile vs Kantree, the Slant community recommends Kantree for most people. In the question“What are the best agile project management tools for software?” Kantree is ranked 4th while JIRA Agile is ranked 10th. The most important reason people chose Kantree is:
Kanban board to drag and drop cards across columns. Select which group type to show as columns: status, milestones, labels, teams, etc (you can create your own dimensions) Set rules to your group (such like auto-assign card to user when dropping a card)
Ranked in these QuestionsQuestion Ranking
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 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 Dynamic kanban view
Kanban board to drag and drop cards across columns.
Select which group type to show as columns: status, milestones, labels, teams, etc (you can create your own dimensions)
Set rules to your group (such like auto-assign card to user when dropping a card)
Pro Infinite hierarchy
Cards can have checklists. Items in the checklist are actual cards, which can be organized in their own board.
Projects is like a tree of card, with unlimited sub-level boards. Perfect to manage complex project with hierarchy. You can choose different settings and user permissions at every level.
Pro Custom card groups
Group your card in unlimited dimensions.
You can use the built-in groups (lists, labels, milestones), adapt them or create your own.
This allows you to manage a projects in other dimensions (by versions, teams, offices, categories, releases, etc).
Visualize your project in kanban and table view, by the group types of your choice.
Drag and drop cards quickly between groups.
Track progress by group types (ideal for managing iterations).
Pro Self-hosted option
Kantree can be installed on your server #privacy
Pro Card models
Use or create card model to best represent your work, for each of your project.
Dozens of types of attributes available, including text, yes/no values, map, file attachments, due date, etc
Perfect to manage projects of different kinds, with multiple card types - like ideas, sales contact, customer feedback, bug report, feature request, bill/order.
Pro Notification (email and in-app)
Pro Slack integration
Pro Github integration
Pro Charts and analytics
Pro Work in progress limits
Set soft limit to group, so that your teams don't get overloaded and lose focus
Adaptative design that is optimize for touch-based interface and adapt the UI to small screen (mobile and tablet)
Pro Table view
Manage your cards in table, by groups.
All the cards are displayed as rows, with their attributes in columns.
Group cards by any group type: milestones, status, team, label, epic, release...
Drag and drop cards across groups.
Pick the attributes to include in the table
Pro Card links
Create linked card to mirror a card in another projects / organization.
Create links with the attributes of the target card, or with its own attributes (to manage a card in multiple boards)
Create custom card relationship: blocked by, same as, etc.
Kantree also support infinite card hierarchy
Pro File attachment
Drag and drop multiple files to your cards at once.
Preview files in a gallery, by card or for the entire project
Con Merely a thin interface to a massive database
Too many configuration details, too confusing, too difficult to search and modify numerous tickets.
User based price model
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.