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.

I like how we can easily create tickets and assign them to the development team with Jira. I also appreciate that it's now integrated with AI, making it easy to rewrite our content. The integration with Teams is great too, as it means we don't have to log into Jira through a browser. We can also integrate Jira with various plugins or use it for test data management, which is pretty handy. Not having to jump between different tools speeds up the development and testing life cycle, which I find really beneficial. If we have access, setting it up is very easy. Review collected by and hosted on G2.com.

if build an inbuilt test data management feature will be very useful for automation testing. Review collected by and hosted on G2.com.

I have been using Jira regularly as part of my day-to-day work for managing bugs, test tasks, and sprint activities in an Agile environment. The biggest advantage is how well Jira supports the complete workflow—from creating user stories and tasks to logging defects and tracking them through different statuses.

As a QA, I find it very useful for linking bugs to user stories, adding detailed reproduction steps, attaching screenshots or logs, and collaborating directly with developers and product owners. The dashboards, filters, and JQL queries help me quickly track open defects, retesting status, and sprint progress without manual follow-ups. Review collected by and hosted on G2.com.

Jira can feel overwhelming at first, especially for new users, because of the number of configuration options and screens. Sometimes simple actions take multiple clicks, and performance can slow down when projects have a large number of issues or custom fields. Reporting customization also requires some learning, particularly when using advanced JQL. Review collected by and hosted on G2.com.

What I like best about Jira is that it brings clarity and structure to complexity.

As a Product Owner, Jira gives me a single, reliable place to translate strategy into execution—epics into stories, ideas into deliverables. It makes work visible, traceable, and measurable, which is critical when you’re managing multiple teams, releases, and dependencies.

What stands out most is:

End-to-end traceability from requirements to delivery

Clear ownership and accountability through workflows and statuses

Real-time visibility into progress, risks, and blockers

The flexibility to adapt Jira to different teams without forcing one rigid way of working

In short, Jira works best when things are messy. It helps me stay in control, make informed decisions, and keep delivery aligned with business value—not just activity. Review collected by and hosted on G2.com.

What I dislike about Jira, from a Product Owner perspective, is that its flexibility can easily turn into complexity and overhead.

Jira can become heavy if it’s over-customized—too many fields, workflows, and statuses end up slowing teams down instead of helping them move faster. Instead of focusing on value delivery, people start managing the tool.

I also find that Jira sometimes rewards process compliance over real progress. A ticket can look “green” while the actual outcome is still unclear or blocked outside the system.

And reporting, while powerful, often needs constant tuning to stay meaningful—otherwise dashboards become noise rather than insight.

In short, Jira is incredibly strong, but without discipline and product thinking, it can drift from being a delivery enabler to a process burden. 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.