The strongest parts are:

Centralized task tracking

Having all work items—bugs, features, improvements, and support requests—in one place reduces confusion and makes it easy to find the latest status on anything. Instead of searching through emails or chat threads, I can quickly see what's assigned, what's in progress, and what's blocked.

Kanban and Scrum boards

The visual boards make it easy to understand team workload and project progress at a glance. For example, during a sprint, I can immediately see which tasks are stuck in review and which are ready for testing, helping the team address bottlenecks before they become delays.

Custom workflows

Being able to tailor workflows to match a team's process creates consistency. For instance, requiring code review and QA approval before a ticket can be marked complete helps ensure quality without relying on people to remember every step.

Powerful search and filtering

Jira's search capabilities save a lot of time. When investigating a recurring issue, I can quickly pull up all related bugs, see their history, and identify patterns that might otherwise be missed.

Dashboards and reporting

Dashboards provide visibility for both team members and stakeholders. Burndown charts, sprint reports, and custom dashboards make it easier to track progress, spot risks early, and communicate project status without manually compiling updates.

Integration with development tools

The ability to link code commits, pull requests, and deployments directly to Jira issues creates clear traceability. When a bug is reported, it's easy to see the associated code changes and determine whether a fix has already been released.

Automation

Simple automations—such as automatically assigning tickets, notifying reviewers, or moving issues between statuses—reduce repetitive administrative work and help keep projects moving without constant manual intervention. Review collected by and hosted on G2.com.

Jira (by Atlassian) is powerful, but it comes with a few well-known pain points—especially once you move beyond small or straightforward projects.

One issue is how quickly complexity can snowball. What begins as “just a board” can turn into layers of workflows, issue types, permissions, and filters. It’s easy to overconfigure Jira to the point where even basic changes start to feel risky.

There’s also the admin overhead. To keep Jira healthy in a larger organization, someone usually needs to actively manage schemes, permissions, automations, and project configurations. Without that ongoing ownership, things tend to drift into inconsistency and messiness.

For non-technical users, Jira often isn’t very intuitive. Even core concepts like epics vs. stories vs. tasks can be confusing, and for non-engineering teams it can feel like you’re learning the system itself rather than simply tracking work.

Performance and overall “heaviness” can become a problem in large instances. In bigger Jira setups—with lots of projects, custom fields, and plugins—it can get slow or cluttered, and searching, loading boards, or applying filters sometimes lags.

Another pain point is the tendency to rely on configuration instead of simplicity. Jira gives you a lot of power, but many teams end up building overly complex workflows when simpler tools or processes would work better. That flexibility can become a trap.

Finally, there’s some UI/UX friction. Small things—like creating issues, switching contexts, or navigating between projects—can take more clicks than necessary. It works, but it isn’t always smooth. Review collected by and hosted on G2.com.

Jira’s biggest strength is its unmatched customization, which lets teams create highly specific workflows that can fit even a complex software development lifecycle. For many users, that power shows up most clearly through robust search capabilities and smooth integrations with tools like GitHub and Slack, which help automate otherwise tedious manual updates. At the same time, the overall experience can become frustrating because of the steep learning curve; new users often feel overwhelmed by a dense, non-intuitive interface.

That complexity can also lead to “admin bloat,” where over-configured projects and too many custom fields make the system feel sluggish and over-engineered. On top of that, Jira’s rigid structure can sometimes favor management reporting over team agility, turning straightforward tasks into a bureaucratic chore. In the end, Jira is still an industry-standard powerhouse for teams that need deep data, as long as they’re prepared to deal with the significant operational overhead that can come with it. Review collected by and hosted on G2.com.

Jira is often criticized for its “click-heavy” interface, which can turn simple updates into a frustrating, multi-step process that drags down day-to-day productivity. That sense of sluggishness is compounded by “admin bloat”: an overabundance of custom fields and rigid global settings that can make the platform feel more like a cluttered database than a streamlined workspace. Many users also resent the “marketplace tax,” feeling pushed into paying for third-party plugins just to get basic functionality that should be native to the software.

Beyond the technical friction, the tool can come across as a “surveillance engine,” prioritizing management’s need for perfect burndown charts over the team’s need for fluid, creative collaboration. Its rigid state machine often fails to reflect the messy, non-linear reality of brainstorming and iteration, creating a disconnect between where work actually happens and where it gets recorded. Ultimately, Jira can feel like a bureaucratic burden—one that asks teams to work for the tool, rather than the tool working for the people. Review collected by and hosted on G2.com.

What I appreciate most about Jira is its flexibility for managing complex workflows while still supporting Agile methodologies. It allows teams to tailor their processes, track tasks efficiently, and keep strong transparency across projects. Tools like Scrum and Kanban boards, in-depth reporting, and smooth integrations with development tools all help boost productivity and collaboration. Jira also provides real-time visibility into project progress and team performance, which makes it easier to spot bottlenecks and improve overall efficiency. Overall, it feels like a comprehensive platform that streamlines project management and supports effective decision-making in fast-changing work environments. Review collected by and hosted on G2.com.

One major drawback of **Jira** is its complexity. The interface can be overwhelming for new users, and the initial setup often takes time and expertise to get right. Performance can also slow down on larger projects, and too much customization may make workflows harder to manage unless there’s proper governance in place. Review collected by and hosted on G2.com.

Jira makes it easy to organize large projects into bite-sized tasks, link projects together, and collaborate not just as a team, but as an organization. Review collected by and hosted on G2.com.

It's not easy to find information in Jira. For example, if you wanted to look through all your closed tasks, there isn't a place for that. You'd have to create a filter and then download an Excel document to share. Once a ticket is closed, it lives on in Jira forever, but is still not easily found. There is room to improve the organization and process of the system. Review collected by and hosted on G2.com.

What we value most about Jira is how clearly it helps us structure and manage technical requests in a traceable way. We use it as our central ticketing system to report bugs, request improvements, and communicate with both our internal tech team and the developers of our CMS.

Jira lets us follow the entire lifecycle of each ticket—from creation through to resolution—across different statuses such as open, in progress, pending QA, or awaiting feedback from our side. Having this level of visibility makes coordination between the editorial, product, and development teams smoother, so nothing gets overlooked and priorities remain clearly defined. Review collected by and hosted on G2.com.

One of Jira’s main drawbacks is that it can feel complex and not very intuitive for non-technical users, especially in a newsroom environment where not everyone is accustomed to working with development tools.

The interface and workflow configuration can be overwhelming at first, and even simple tasks can take more steps than you’d expect. For editorial teams, this can slow adoption, create friction in day-to-day use, and ultimately make Jira feel less user-friendly than simpler ticketing or communication tools. Review collected by and hosted on G2.com.

I am not opening Jira just to do my job. I open it to see the progress, control, and current status. It is where I know things are really going somewhere, as opposed to talking about what should happen but not actually doing it. Every ticket gives me an idea of how things are developing, who contributed to this development, and what problems there are along the way. Review collected by and hosted on G2.com.

Sometimes it slows down due to the level of details you need to include into even one log. There must be sufficient context to provide a clear explanation of what has been done at that point in time to help understand its significance in the future. Review collected by and hosted on G2.com.

Jira’s strongest feature is its extensive customisation. It lets you build detailed workflows and custom fields tailored to your team’s specific needs. It also offers robust Agile-focused reporting, such as burndown charts and velocity tracking, which provide valuable insight into overall project status. On top of that, its seamless integration with developer tools like Bitbucket and GitHub makes the transition from task management to code delivery much easier. Review collected by and hosted on G2.com.

For smaller teams, Jira’s pricing can feel excessive, especially because costs can climb quickly once you start adding the necessary plugins from the Atlassian Marketplace to fill functionality gaps. For simpler projects, the ongoing administrative overhead often comes across like a “management tax,” even though the ROI can be strong for large enterprises that truly need complex tracking and deep reporting. Ultimately, you may end up paying for a powerful feature set that your team barely uses. Review collected by and hosted on G2.com.

Project tracking is very easy, with unmatched flexibility and deep integration across the software development lifecycle. Review collected by and hosted on G2.com.

Low performance: Many users find the web interface bloated and sluggish. Pages often take several seconds to load, and certain actions such as changing a ticket type can kick off background jobs that slow things down even more and interrupt the workflow.

Overwhelming complexity: Because Jira is so flexible, it can easily turn into a maze of tabs, menus, and tucked-away features. For new users, the learning curve is steep, especially with specialized jargon like “Epics,” “Sprints,” and “Schemes.”

“Click-heavy” UI: Recent interface updates (including those in 2025 and 2026) have been criticized for burying key functions and forcing users to click through more steps to complete everyday tasks. Review collected by and hosted on G2.com.

In my current project, Jira has been very helpful in keeping everything organized. I mainly use it to track tasks, bug and sprint progress, and it gives a clear picture of what's going on it the team at any time.

I really like the way boards are structured, especially for sprint planning and daily tracking. it becomes easy to prioritizes work and move tasks across different stages. Also, the ability to customize workflows and fields make it flexible enough to fit different type of projects. Review collected by and hosted on G2.com.

One thing I noticed is that is the Jira can feel a bit complex when you first start using it. there are many features and settings, so it takes time to get comfortable with it.

Also, if workflows are not designed properly, things can become confusing instead of helpful. Keeping it simple is important, otherwise it may slow down the process. Review collected by and hosted on G2.com.

I like Jira's customizable workflows and issue tracking capabilities. It helps development, QA, and product teams work in a structured manner and provides visibility into the entire project lifecycle. User stories, tasks, bugs, and epics can be managed in one place. The features for sprint planning and backlog management are effective. Workflows can be customized according to the team's processes, there are powerful filters, dashboards, and reports that help track project progress. Additionally, integration with tools like Confluence and Zapier Square makes its functionality even more available. For me, the most valuable feature is issue traceability, which allows easy tracking of development, tasks, test cases, and bugs related to any requirement. This improves coordination between QA, development, and product teams and makes release management more organized. The biggest advantage is that the entire team has real-time visibility of the project, making planning, execution, and delivery more efficient. Review collected by and hosted on G2.com.

Now working on Jira feels quite right to me, there aren't many shortcomings for me, but there are some things that cannot be ignored. One of these things is that there is quite a lot on its dashboard, so a new person who is onboarding might face some difficulties. Then there is no way to export the workflow. The biggest challenge is its complexity management; Jira is extremely flexible, but if teams create too many workflows, custom workflows, issue types, and fields, maintaining the system and onboarding new team members can become difficult. Review collected by and hosted on G2.com.