When comparing JIRA Agile vs Worksection, the Slant community recommends JIRA Agile for most people. In the question“What are the best online Kanban tools?” JIRA Agile is ranked 11th while Worksection is ranked 21st. The most important reason people chose JIRA Agile is:
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.
Ranked in these QuestionsQuestion 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 Low prices and free options
Prices are really low as paid plans start at $9 per month and they don't depend on users quantity. There is a free plan for up to 2 projects and a premium plan if free for social and educational projects.
Pro Great features list
There are lots of features for tasks and subtasks management, for reports and billing, for costs and time control, handy calendar and Gantt chart, etc.
Pro Lots of small features for handy using
Like bulk copy, bulk tasks creation, drag-and-drop tools, templates, etc.
Pro Intuitive interface
It's very easy to be used even for those who aren't on close with computers. And support team answers quickly if still there are some questions.
Pro Lots of tools for systematization
There are customizable statuses and tags, priorities for tasks and subtasks and star marks for important projects. You can also split tasks in groups.
Pro Good communication system
All the tasks and subtasks can be commented. You can restrict access to any task, subtask or comment. Any documents, images and video can be attached. And you can preview them or edit document right in the system without downloading.
Pro Good deadlines control tools
Handy calendar and Gantt chart. Start and finish dates can be set for tasks and subtasks, tasks and subtasks dependancies can be set. Tasks can be created or their timing can be changed right in the Gantt chart. There is a Google Calendar sync and export to iCal possibility. Notifications can be sent in the system or to email.
Pro Easy to access
Works via any browser, there are iOs and Android mobile apps.
Pro Data export
Project data can be export into XML format
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.
