Jira’s biggest strength is its core simplicity. While other project managers overcomplicate the basics, Jira keeps the foundation clean. If I just need to spin up a quick task, map out child issues, or drop a comment, it’s completely frictionless. However, as someone who treats software and workflows as a craft, I really enjoy how deep the customization goes. It has evolved to include modern agile features, letting you build out a robust, tailored system without sacrificing that clean, out-of-the-box ease. Review collected by and hosted on G2.com.

The reliability of the comment editor when handling rich media. I frequently need to attach screenshots or video recordings to properly document an issue, but Jira sometimes fails to process these uploads and does so silently.

There is no error message or warning—I will hit save, assume the update is securely logged, only to realize the next day that the entire comment is completely missing. The platform really needs better error handling and clear UI feedback when a rich-media attachment fails to upload. Review collected by and hosted on G2.com.

What I like best about Jira is its ability to organize and track work efficiently across teams. It provides a clear view of tasks, project progress, sprint planning, and issue tracking in one place. The customizable workflows, dashboards, and integration with development tools make collaboration smoother and help teams stay aligned on priorities and deadlines. It is especially useful for managing agile projects and improving overall project visibility. Review collected by and hosted on G2.com.

One thing I dislike about Jira is that it can sometimes feel overly complex and difficult to navigate, especially for new users or smaller teams. Customizing workflows and managing permissions can become time-consuming, and the interface may feel cluttered when handling large projects. Additionally, performance can occasionally slow down with extensive boards, filters, or integrations. Review collected by and hosted on G2.com.

The ability to manage multiple stories, task in one single unified place is great to work. Jira helps project tracking much easier, collaboration, communication within the team is effective. One unified dashboard helps to view different types of chart, report, progress, linking items to parent task, sprint chart and so on. Review collected by and hosted on G2.com.

As per latest jira update. I could see certain options or settings are grouped under hidden elements which is quite difficult to find it out. As a first time user, I felt too many level of configuration so I might get lost in some point. Review collected by and hosted on G2.com.

I would rate Jira a 9 out of 10. At Pliant GmbH, it was a core part of how we managed engineering, product, and operational workflows—especially sprint planning, backlog management, incident tracking, and coordinating cross-functional projects.

One of its biggest strengths was the flexibility and the integration ecosystem. Connecting Jira with Confluence, Slack, GitHub, and our deployment workflows made it much easier to link technical work, documentation, and operational processes in a single system. For example, during payment infrastructure updates or API feature rollouts, teams could track development progress, blockers, deployments, and incidents in a structured, consistent way.

The main reason I wouldn’t give it a full 10 is that Jira can become complex and harder to manage as workflows scale. Custom workflows, permissions, and board structures sometimes required ongoing maintenance, and for non-technical teams the interface could occasionally feel overwhelming compared with lighter project management tools. Review collected by and hosted on G2.com.

One thing I dislike about Jira is that it can become overly complex as workflows and teams scale. At Pliant GmbH, different teams—such as engineering, product, operations, and compliance—often used customized workflows, boards, and ticket structures, which sometimes made navigation and day-to-day project management harder than it needed to be.

Another challenge was the ongoing maintenance required for workflows, permissions, and overall issue organization. As projects grew, boards could get cluttered with tickets, dependencies, and custom fields, and it became difficult to keep a clear overview without frequent cleanup and active process management.

For non-technical teams in particular, Jira could feel less intuitive than lighter collaboration tools. Even though it’s very powerful for engineering work and operational tracking, simpler workflows sometimes ended up requiring more configuration than I expected.

Lastly, setting up reporting and dashboards often took extra customization to produce meaningful insights for different departments, especially in fast-moving operational environments like payment infrastructure and incident management. Review collected by and hosted on G2.com.

I use Jira to manage all my projects and track the engineering work. Jira is great for handling project updates and overseeing what projects and tickets engineers are working on. I like that all my projects are managed in one place with the team, components, and labels, so I don't have to switch between multiple tools. I can create filters and look at the status of projects and tickets which is super handy. The filters are really important for me as they help me focus on what matters most and help in tracking projects effectively. Review collected by and hosted on G2.com.

So the whole navigation is very overwhelming. And that has to be fixed. Second is the links that come on Slack. I have integrated Jira into my Slack. So let's say someone sends a link in the Slack. Right? So that doesn't open in the Jira app on the phone. Rather, it opens on the web page where I have to do the single sign off. Is a lengthy process. Every time, like, ticket comes very frequently. Like, every fifteen minutes or every fifteen minutes, I have to log in. Rather if it opens on the app, it solves very good problem for me. So that needs to be now what I have to do is I have to, like, look for that number, open the Jira app, look for like, find the search option, then search that ticket, and then open. This is a huge user journey I'm missing out. And sometimes we use it with Google Sheets to only, like, pull all the tickets into Google Sheets and do some calculations which Jira is missing again. So that needs to be there. Review collected by and hosted on G2.com.

Jira is a very convenient and easy tool for tracking the entire lifecycle of a task, from planning to getting it live in production. It helps the whole team track delivery and productivity throughout the sprint. I’ve found it especially helpful for keeping both product and technical tasks organized and ensuring they get delivered on time. It’s also integrated with Jenkins and the CI/CD pipeline, which sends notifications when tasks go live. Review collected by and hosted on G2.com.

Sometimes, changes to a task’s status take a bit of time to show up in everyone’s account. This latency can occasionally last around a minute, but it doesn’t seem to go beyond that. A similar issue happens when assigning a task to a team member. It can take a little while for them to be notified and for the assignment to appear on their dashboard. Review collected by and hosted on G2.com.

Jira is one of the best project management tools available. It excels at team collaboration and enables real-time tracking of progress across projects, which has been invaluable for our Project Managers, Product Owners, and Tech Leads in handling heavy workloads. It keeps every team member and stakeholder on the same page regarding project progress, which dramatically reduces miscommunication. Jira is excellent for Sprint Management and Backlog Management, and the ability to clearly define an owner for every action item ensures accountability across the team. Custom workflows, dashboards, and reporting make it easy to visualize where we stand at any point. Overall, Jira has become indispensable for running agile projects efficiently. Review collected by and hosted on G2.com.

There is not much to dislike. The learning curve can feel steep for new users due to the depth of configuration options and customization. Performance can occasionally slow down on very large projects with heavy dashboards. Pricing can also add up for larger teams. Overall though, the value Jira delivers far outweighs these minor downsides. Review collected by and hosted on G2.com.

What I personally like about Jira is that it keeps engineering work organized and visible across teams. In production support and SRE environments, multiple teams work together during deployments, incidents, and RCA activities, so having proper tracking becomes very important.

I’ve mainly used Jira for:

incident tracking

sprint tasks

deployment activities

RCA follow-ups

operational improvements

One thing I find useful is that everybody can track the status easily instead of depending on chats or calls. During production issues, Jira helps track ownership, priority, timelines, and pending actions properly.

I also like the integration aspect. For example, we used Jira along with CI/CD workflows and monitoring alerts so teams could track issues and changes more systematically.

Overall, it helps reduce confusion and improves coordination between developers, SRE, QA, and platform teams. Review collected by and hosted on G2.com.

One thing I feel about Jira is that sometimes it can become overly process-heavy if workflows are not designed properly. In fast-moving production or SRE environments, too many ticket states, approvals, or mandatory fields can slow down execution during critical situations.

I’ve also seen cases where teams create too many low-value tickets, which makes backlog management noisy and difficult to prioritize effectively.

Another challenge is that if dashboards and workflows are not maintained properly, Jira can become more of a tracking tool than an actual productivity tool.

That said, when workflows are kept simple and aligned with operational needs, Jira works really well for collaboration, incident tracking, and engineering coordination. Review collected by and hosted on G2.com.

I particularly like Jira's AI-powered features, such as AI-generated issue summaries and assistance with creating or refining tickets, which help reduce manual effort. The improved Dashboards and Atlassian Analytics also provide better visibility into sprint progress, team workload, and project health. Another useful enhancement is the expanded Automation capabilities, allowing more complex no-code rules to automate repetitive tasks like issue assignment, status transitions, and notifications, helping teams save time and maintain consistent workflows. Review collected by and hosted on G2.com.

Filter creation and saving it with permission is very complex. Their is no proper guide on making automation rules. Review collected by and hosted on G2.com.

The thing I keep coming back to is the custom workflows. Once you've set them up just right for your team, it kind of clicks — like, this is exactly how we work, and now the tool actually reflects that. It stops feeling like you're bending your process to fit the software and starts feeling like the software finally gets you. Review collected by and hosted on G2.com.

Ugh, the performance. It can be so sluggish sometimes you click something and just sit there waiting. When you're in a flow and trying to quickly update a few tickets, that lag is genuinely frustrating.

And the configuration is a beast. Like, it's powerful, don't get me wrong, but there's a point where you just want to do something simple and you end up three menus deep wondering how it got this complicated. Review collected by and hosted on G2.com.