There are none, because Jira does a million different things, not necessarily all that well though. Jira can be a task manager, a bug tracker, a service desk t

There are none, because Jira does a million different things, not necessarily all that well though. Jira can be a task manager, a bug tracker, a service desk ticketing system, a project planner (regardless of methodology applied), a Kanban board, a knowledge database and so much more if you know how to configure it. That's also why sucks in many cases. You end up in these weird situations where you have a service desk ticket marked as an Epic, or on person on the team uses a kanban board, while the rest are just going by a different priority. Sometimes priorities migrate from you service desk to a SCRUM project and things make no sense. You can work pretty well with Jira, if you can stick to one set of feature and keep the entire organisation locked to one type of projects. There are some things it's not good for, I don't see it as being a good project planing tool, regardless of how you try to use it. As a service desk tool it's pretty good. I will say Jira is much better something like Phabricator or Bugzilla. Neither of those are alternatives, Phabricator is the closet, but it still doesn't do all the things Jira does.