Review Summary
Users appreciate Jira for its highly customizable workflows, robust project tracking capabilities, and seamless inte ...
Users appreciate Jira for its highly customizable workflows, robust project tracking capabilities, and seamless inte ...
Atlassian's mission is to unleash the potential of every team. We make agile & DevOps, IT service management and work management software to help teams organize, discuss, and complete shared work. Over 300,000 companies of all sizes worldwide rely on Atlassian to help their teams work better together and deliver quality results on time
Do You Manage Peer Insights at Atlassian?
Access Vendor Portal to update and manage your profile.
The thing I like the most about Jira is its flexibility and custimizability. It provides customization of workflows, issue types and dashboards so it can cater for different project requirements which is a big advantage. And ther's also the ability to connect with other tools like Confluence and Slack, which can help streamline communication and keep track of progress on projects.
- The kanban board is very flexible and it fits exactly the way my team works. - Other teams prefer other workflows, and JIRA supports this as well. - Plenty of features: filters, epics, task types, good formatting of ticket descriptions, integration with Github.
Drag and drop backlog / sprint functionality. Easy to customise. Top keyboard shortcuts allowed
The part I hate the most about Jira is learning curve it has for people who are new to it. It is overwhelming at first because there are so many settings and customization options but you will be better of if you invest the time. Also, while potent, its display can get a bit messy at times. Some can also find the mobile app to be not as user-friendly as the desktop version, which hinder its on-the-go use.
- JIRA's UI is clunky and hard to use. - Too opinionated in some cases. - It feels heavyweight.
Some fiddly ux especially from backlog/sprint views, eg needing to click on very small icons to action changes. ticket creation requires a loading / wait from the user before the ticket appears in the backlog (although can be circumvented by the great ticket split feature!)