Jira

What do you like best about the product?

We use Jira daily and rely on it for our main software development activities. All of our engineering department uses it every day, so without it. the business would stop. I like enormous configurability of Jira that basically allows us to suit it to every possible need.

What do you dislike about the product?

Sometimes that advanced configurability can become a downside, because it will require time and effort to find and do what you need.

What problems is the product solving and how is that benefiting you?

Software development mainly. Then documentation and process improvement. We also use Service Desk.

What do you like best about the product?

It's good for ticket management/task tracking

What do you dislike about the product?

Properly configuring it takes a long time and is not easy to do

What problems is the product solving and how is that benefiting you?

Team task management/tracking, both for tech and non-tech teams

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

Jira tackles the core problem of fragmentation by bringing scattered tasks, documents, and conversations into one centralized, searchable source of truth that keeps diverse teams aligned. It helps prevent “systemic drift” by offering real-time visibility into planned versus actual progress, so roadblocks can be spotted early—before they derail a deadline. For me, that translates into a major reduction in manual busywork: instead of chasing status updates across email threads or Slack messages, I can rely on automated workflows to keep work moving.

It also supports capacity management by making it easier to see when people are overbooked across multiple projects at the same time, which helps reduce the risk of burnout. And by integrating directly with development tools like GitHub and Confluence, Jira keeps the context behind decisions close at hand, so I spend less time hunting for lost information and more time on high-value work. Overall, it turns chaotic, non-linear projects into more structured, predictable delivery pipelines that support both the team’s sanity and the project’s success.

What do you like best about the product?

Jira for its exceptional customization, robust Agile project management capabilities.

What do you dislike about the product?

Dislikes of Jira for some users it is to complex, the UI is cluttered and hard to configure for some users

What problems is the product solving and how is that benefiting you?

It solves the problem of scattered task management by centralizing work into trackable tickets with clear ownership, priorities, and status

What do you like best about the product?

We can easily create information even with minimal input, and tickets are created within seconds. It’s easy to access the system and pull data, and the bulk assign option is a good feature. The self dashboard feature is also helpful because it lets me view all details on the same page.

What do you dislike about the product?

Everything is good. I haven’t observed any dislikes related to Jira so far.

What problems is the product solving and how is that benefiting you?

We were able to resolve the ticket with a simple comment, and it was easy to bulk-assign and resolve tickets within a few minutes. The self ticket is easy to access, and the details are appropriate and helpful for finding the Jira.