Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariJIRA Agile vs Zenkit
When comparing JIRA Agile vs Zenkit, the Slant community recommends Zenkit for most people. In the question“What are the best online Kanban tools?” Zenkit is ranked 6th while JIRA Agile is ranked 11th. The most important reason people chose Zenkit is:
Easy to use and easily understandable for everyone.
Specs
Question Ranking
Pros
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.
Pro Powerful and simple to use tool with a clean design
Easy to use and easily understandable for everyone.
Pro Many important data views
Data views include Mind-Map, Kanban-Board, Spreadsheet, List, and Calendar. Views can be switched easily.
Pro Native apps
Native apps for iOS, Android, macOS, Windows, and Linux.
Cons
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.
