Jira Reviews & Product Details

I like most about is that i use it everyday and it is the best tool for the task management. The implementation took a bit of planning but it was not difficult and the customisation options were worth it . The set of features from boards and sprints to report and automation rules and i end up using it almost everyday. It also integrates well with the other tools i use like github. Their customer support was professional and quick to respond. Review collected by and hosted on G2.com.

It can feel overwhelming at first because there are so many settings and configurations. If you are managing big projects or lot of plugins it sometimes feels a bit slow. Also setting up custom workflow can take more time than expected. Review collected by and hosted on G2.com.

What I like best about Jira is that I can create projects, and whenever there is a new feature requirement, we can create a ticket for that task and assign it to specific teammates. We can also track the ticket status, and the workflow is fully customizable based on our process. In addition to that, Jira provides clear visibility into progress through boards, filters, and reports, which makes it easy to track sprint progress and identify blockers early. Another thing I like is the collaboration and documentation support. Comments, attachments, and activity history help keep all discussions and updates in one place, so nothing is missed. Review collected by and hosted on G2.com.

One thing I dislike about Jira is that when I first started using it, it felt very complex and overwhelming. The UI has a lot of options, and it takes time to understand how everything works. However, after using it daily, I got used to the interface. Another issue is that sometimes the drag-and-drop functionality for tickets is not very smooth, especially when boards have many columns or filters applied. In addition, Jira can feel heavy and slow at times, particularly on large projects with many tickets and custom fields. Also, too much customization can sometimes make workflows confusing, especially for new team members who are not familiar with the project setup. Review collected by and hosted on G2.com.

What I like most about Jira is how well it handles complex workflows. It’s very flexible when it comes to creating issues, tracking progress, and managing sprints. Once things are set up properly, it gives clear visibility into what’s being worked on, what’s blocked, and what’s coming next, which is really helpful for cross-functional teams. Review collected by and hosted on G2.com.

The biggest downside for me is that Jira can feel overwhelming, especially for new users. There are a lot of settings, fields, and options, and it’s easy to get lost if you’re not familiar with it. Sometimes performance can also feel a bit slow, particularly on large projects with many tickets. Review collected by and hosted on G2.com.

The main thing for me is the transparency it gives our client. When we are in the middle of a messy SAP EWM integration things get lost in email way too easily. I like that I can link a specific MM configuration ticket directly to the functional spec in Confluence. It saves me from having to explain the same logic to the offshore team five times. Also the bulk edit feature is a lifesaver when the client changes their priority on 40 different warehouse testing scripts at once. It just works and doesn't require a lot of overhead. Review collected by and hosted on G2.com.

Honestly? The notifications are a nightmare. If I do not spend an hour silencing the noise my inbox just becomes a Jira graveyard. And do not get me started on the loading times for Advanced Roadmaps when you have more than 500 issues in a plan. It gets sluggish. Also for something that is supposed to be agile setting up a new workflow for an SAP transport process feels way too rigid. You basically need a PhD in JQL just to pull a report that shows me which IDocs are actually blocking our UAT. Review collected by and hosted on G2.com.

The best part of Jira is its flexibility in handling Agile workflows. As a Product Manager, the ability to seamlessly toggle between Kanban boards, high-level Roadmaps, and the backlog makes sprint planning much easier. The integration with development tools (like Bitbucket/GitHub) is excellent, allowing us to link code commits directly to tickets so we always know the status of a feature without bothering the developers. Review collected by and hosted on G2.com.

The learning curve is quite steep for non-technical team members. The interface can feel cluttered and sluggish at times, especially when loading complex boards with many custom fields. Configuring permissions and workflows is also overly complicated; you often need a dedicated Jira Admin just to make simple process changes without breaking something else. Review collected by and hosted on G2.com.

What I like most about Jira is its clean and simple interface. It’s easy to use and access, even for someone new. I also like how smoothly it integrates with tools like Slack, which makes communication faster. The automation features for updates and responses save a lot of time, and it works well when coordinating tasks across different teams. Review collected by and hosted on G2.com.

What I dislike about Jira is that it can sometimes feel a bit slow, especially when there are too many tickets or custom fields. Also, too many notifications and frequent updates can be distracting, and for small or simple tasks it can feel more complex than necessary. Review collected by and hosted on G2.com.

For a DevOps team, the Ease of Integration is the absolute best feature. Connecting Jira to our CI/CD pipelines (like Jenkins and GitHub) means ticket statuses update automatically when code is merged, which saves us hours of manual work. The Number of Features regarding reporting and agile boards is extensive, allowing us to track sprint velocity accurately. Because of this connectivity, my Frequency of Use is constant; it is the dashboard I have open on my second monitor all day. Review collected by and hosted on G2.com.

The Ease of Use leaves a lot to be desired. The interface can be sluggish and navigating the complex settings menus is often confusing for new team members. Similarly, the Ease of Implementation for custom workflows is low; you really need a dedicated admin to set up schemes correctly, or you risk breaking the project configuration. Regarding Customer Support, I often find myself relying on community forums rather than official channels because ticket response times can be slow Review collected by and hosted on G2.com.

What I appreciate most about Jira is the balance it strikes between structure and flexibility. It provides a clear overview of work spanning backlogs, sprints, and releases, yet still lets teams tailor workflows to fit their actual processes. The transparency into status, ownership, and dependencies goes a long way in minimizing ambiguity, and the reporting features—such as burndown charts, velocity, and sprint health—make planning and retrospectives much more data-driven. All in all, Jira helps align product, engineering, and stakeholders without the need for constant follow-ups. Review collected by and hosted on G2.com.

What I find challenging about Jira is that it can be overwhelming and cumbersome, particularly for newcomers or teams outside of engineering. The abundance of fields, screens, and configuration options can make straightforward tasks seem unnecessarily complex. Additionally, performance tends to slow down on larger projects, and managing workflows, permissions, and custom fields often demands significant administrative effort. As time goes on, Jira instances may become cluttered, which affects usability and makes it more difficult to maintain consistency across different teams. Review collected by and hosted on G2.com.

Jira offers powerful and flexible project management capabilities, particularly for agile teams handling complex workflows. Despite its depth, once users become familiar with the platform, it supports frequent daily use through reliable issue tracking, Scrum and Kanban boards, and strong automation features. Customizable workflows, dashboards, and reporting improve visibility and consistency across teams. Jira’s seamless integrations with tools like Confluence, GitHub, Bitbucket, and Slack reduce context switching and enhance productivity. Over time, Jira becomes an essential, centralized system that teams rely on continuously to plan, track, and deliver work. Review collected by and hosted on G2.com.

Jira’s biggest drawback is its ease of use, especially for new or non-technical users. The learning curve is steep, and initial setup—including workflows, permissions, and custom fields—can be time-consuming. The interface can feel cluttered, making everyday navigation less intuitive, particularly for users who access Jira frequently throughout the day. Performance issues may arise in larger or heavily customized instances, and excessive configuration can make long-term maintenance challenging. Additionally, costs can scale quickly, and customer support and documentation are sometimes inconsistent for advanced use cases. Review collected by and hosted on G2.com.

The platform offers efficient task prioritization and provides detailed project visibility, allowing for agile workflow customization. Real-time progress tracking is available, along with seamless integration for developers. Its robust reporting analytics and automated recurring tasks help maintain clear accountability. Additionally, the system supports scalable issue management and thorough backlog grooming, making it a comprehensive solution for project management. Review collected by and hosted on G2.com.

The interface is highly complex, with an overwhelming number of configuration options that can make it difficult to navigate. Performance tends to be slow, especially when working with large boards, and the user interface often feels cluttered. The onboarding process is steep, and the rigid hierarchy structures can be limiting. There is also a lot of notification noise, which can be distracting, and bulk editing is challenging to manage. Additionally, handling dependencies is often cumbersome, and the premium add-ons are quite expensive. Review collected by and hosted on G2.com.