Jira Reviews & Product Details

Jira’s biggest strength is its flexibility. It allows teams to customize workflows, issue types, and dashboards based on how they actually operate. The visual boards—Kanban and Scrum—make it very easy to track progress across teams. Integrations with tools like Confluence, GitHub, Bitbucket, and Slack also make collaboration seamless. I like that everything from sprint planning to release tracking can happen in one place. The reporting features, especially burndown charts and velocity tracking, help teams plan better and continuously improve. Review collected by and hosted on G2.com.

Jira can feel heavy and complicated, especially for new users. The interface has a learning curve, and setting up workflows or permissions requires a lot of configuration. It can also become slow when dealing with very large projects or too many custom fields. Some features feel hidden behind multiple menus, which affects ease of use. Pricing can also become a downside for teams that scale quickly, as costs rise with user count. Review collected by and hosted on G2.com.

What I like most about Jira is how powerful and flexible it is for managing projects of any size, from small teams to large enterprise workflows. Jira gives complete visibility over tasks, issues, and sprint cycles, making it easy to understand who is doing what and how far along the work is. Its customizable boards, workflows, and permissions allow teams to adapt Jira to their exact process rather than forcing them into a fixed structure. Review collected by and hosted on G2.com.

Jira's biggest drawback is its complexity. For new users, the interface can feel crowded with options, menus, and settings, which leads to a learning curve. Setting up custom workflows, screens, and permissions often requires admin experience and can take a lot of time. Sometimes, even simple actions feel more complicated than necessary because Jira tries to support every possible scenario. Review collected by and hosted on G2.com.

What I like best about Jira is its ability to bring complete structure and clarity to even the most complex projects. The platform is built in such a flexible way that it can adapt to any team's workflow, whether it's agile, scrum, Kanban, or a fully customized process. One of its biggest strengths is how it connects every stage of development from initial planning to execution and deployment into a single for priority, labels, linked issues, and sub-tasks. Review collected by and hosted on G2.com.

While Jira is powerful, one of the main drawbacks is that it can feel overwhelming, especially for new users or non-technical teams. Its interface is packed with menus, features, and customization settings that require time to understand. Sometimes, simple tasks like modifying a board, adjusting a workflow, or configuring issue types. Review collected by and hosted on G2.com.

the most important thing i like in Jira is its impressive UI , its feels so modern and minimal , it been more than 2 years using Jira but still it feel fresh design. it allows us to break down massive complex ETL/ELT projects into manageable, trackable nuts, we can create custom issue types and custom workflows, and also ticketing is crucial for managing dependencies. it gives me and my manager instant, clear visibility . the integration with GitHub is best, as i commit changes, the commits are automatically visible in the jira ticket. we use this process daily on Jira. Review collected by and hosted on G2.com.

the tool is powerful but that power means its easy to make a mess if you dont have a dedicated expert admin , simple things like changing a workflow step or adding a new board can be a huge headache. but overall its a great tool . Review collected by and hosted on G2.com.

I like that Jira makes technical work traceable. Features, bugs, design discussions—they all live in one place, so nothing slips through the cracks. The workflow engine is predictable, and once it’s configured properly, it forces structure in teams that would otherwise drift. The integrations with Git, CI/CD, Slack, and Confluence reduce context-switching, which saves real time. It isn’t pretty, but it’s reliable, and reliability wins in engineering work. Review collected by and hosted on G2.com.

Jira’s biggest weakness is speed. Large projects, heavy boards, or complex workflows make the interface crawl. Simple actions—opening an issue, switching filters, loading a board—take longer than they should. That latency breaks focus, especially when you’re moving fast in an engineering workflow. The tool is powerful, but the performance overhead gets in the way of actually getting work done. Review collected by and hosted on G2.com.

Recently, I’ve started appreciating how much better the automation and rule-based triggers have gotten. Small things like auto-assigning tasks, updating statuses, and sending reminders save a lot of time. I also like the newer UI refinements—boards feel faster, and switching between issues is much quicker now. Overall, it’s become even more convenient for day-to-day work. Review collected by and hosted on G2.com.

The only thing that still feels a bit overwhelming is the deeper configuration part. Setting up workflows or permission schemes can get confusing if you’re not experienced with Jira. A more beginner-friendly setup guide or simpler templates would definitely help new teams get comfortable faster. Review collected by and hosted on G2.com.

I have been using Jira for the past year, and what I appreciate most is its tracking capability. We rely on it for managing tech-related issues, and whenever any team creates a Jira ticket, it becomes very easy to track and resolve the issue quickly. Anyone can update the ticket through other software as well, which adds to its convenience. Jira is also beginner-friendly and very easy to use, from creating a ticket to assigning it. Overall, it is a wonderful software. Thank you, team Jira. Review collected by and hosted on G2.com.

I haven't found anything wrong with it so far. It has been helpful in completing my tasks and resolving issues, which is important both for me and my team. I have no negative thoughts about it. Review collected by and hosted on G2.com.

The strongest advantage of Jira is how customizable and adaptable it is. Teams can modify workflows, screens, fields, and permissions to match exactly how their process works. Scrum teams benefit from its sprint boards, burndown charts, backlog grooming, and story point tracking. The ability to integrate with tools like GitHub, Bitbucket, Slack, Confluence, and CI/CD systems makes Jira a central hub for planning and tracking work from start to finish. Review collected by and hosted on G2.com.

Jira's biggest drawback is its complexity. The interface can be dense, especially for new users who see many menus and configuration options. Setting up workflows, screens, and custom rules might require deep knowledge or admin support. If a workspace has been poorly configured over time, Jira can become cluttered with unnecessary issue types, long forms, and confusing statuses. Review collected by and hosted on G2.com.

What I like most about Jira is how well it organizes the entire workflow for our team. Tasks, Bugs, sprints, everything stays in one place. The agile boards are extremely easy to follow, and it becomes clear very quickly who is working on what and where the bottlenecks are. The customization options are a big plus. You can design your own workflows, create custom issue types, and adapt Jira to match the team's style instead of forcing everyone into a fixed structure. Integrations are solid as well... IT connects smoothly with slick, github, Bitbucket, confluence and even design tools. I personally didn't integrated it with other software but the dev team and managing team had experience and they they have good feedback about it. Getting started was easier than expected, with ready-made project templates and guided setup our team and running quickly. The documentation and community support are impressive. Even when we had questions about workflow or automations, we found answers almost immediately. We used Jira almost daily.... from backlog grooming and sprint planning to tracking bugs and releases. It has basically become the backbone of our project workflow. Review collected by and hosted on G2.com.

The interface can feel overwhelming at first, I mean the first time I logged in it does feel like that. It took some time to get accustomed. Even our new team members who are not familiar with agile tools. Some advanced configurations also require more time to understand. Performance can slow down a bit with very large projects. Review collected by and hosted on G2.com.

The best part about Jira is its depth and flexibility. You can customize everything: workflows, issue types, fields, automations, permissions, and boards. This means a team can design Jira exactly the way their process works. The Agile boards are especially helpful for teams can plan sprints, track progress in real time, and manage backlogs with full visibility. Review collected by and hosted on G2.com.

The interface can feel overwhelming, especially for new team members. There are so many menus, configurations, and nested options that onboarding becomes difficult. Sometimes, even experienced users struggle to locate workflow settings or custom fields. When too many custom rules or automations are added, Jira can also slow down or become hard to maintain. Review collected by and hosted on G2.com.