In reply to Chris Fitzgerald.
I believe that is exactly the heart of the problem. The comparison on price. It’s like saying “a bike only costs $100 while this Ford F150 costs $70.000, so choose the bike”. Knowing that the instance you try to load up your complete toolset on the bike, it’ll instantly fall short.
RTM and Todoist are fine tools, but they’re just “tasklist tools”, which happen to be able to also compartmentalize things into sort of a folder called projects. You comment, assign all that. It’s fine. They’re great for that. But that’s a very basic need.
JIRA is so much more. It has project models, so you can customize which project has which issue types, and what should happen during transitions, which fields should show when. It lets you model a project, so everything happens according to how we’ve agreed a project should be running.
It supports both Kanban and Scrum. It has backlogs, estimates, roadmaps, sprints, boards, filters, charts and reporting, you name it. You can of course just use a simple project as is. But you can also design your project from the ground up, to support how your processes work.
And, you can integrate it with Confluence, for knowledge work. With chat tools for communications. With development tools. You name it.
So to compare such simple tools with a platform like JIRA, simply isn’t a reasonable comparison for any of the tools. They’re that far from being the same.