Jira Reviews & Product Details

Jira is the ultimate truth that transforms chaotic sticky-note enrgy into a streamline, high-visibility workflow. It's robust customizability allows teams to mould every issue and board to their specific needs. also the way it integrates deep technical data with high-level project tracking makes it perfect bridge between granular dev work and bigg-picture strategy. Review collected by and hosted on G2.com.

Sheer complexity of its configuration can turn a simple setup into a labyrinth of admin-only permission and hidden settings. Frequently suffers from noticeable UI lag and notification fatigue where sheer volume of pings can bury the actual work. Ultimatelt, it often feels over-engineered for smaller team, demanding more time spent "feeding the tool" than actually shipoping code Review collected by and hosted on G2.com.

What I like best about Jira is how it brings structure and clarity to complex workflows while still being highly customizable.

On the UI/UX side, the Scrum and Kanban boards with drag-and-drop make task tracking very intuitive. I’ve personally found that organizing tasks into sprints and visually moving them across stages helps reduce confusion and saves time during daily standups.

Integrations are another strong point. Jira connects smoothly with tools like GitHub and Slack, which means updates from commits, pull requests, and team discussions are all linked in one place. This reduces context switching and keeps the whole team aligned without extra effort.

In terms of performance, it handles large projects reliably, and I rarely face major slowdowns even with many issues and users.

For pricing and ROI, while it might feel a bit expensive for small teams at first, the time saved through automation, organized workflows, and better team coordination makes it worth the cost. It reduces manual tracking and improves overall productivity, which directly impacts delivery speed.

Support and onboarding are also solid. There’s extensive documentation, templates, and community resources that make it easier to get started, even if you’re new to project management tools.

Regarding AI and intelligence, Jira has started introducing smart features like automation suggestions and predictive insights, which help in prioritizing tasks and reducing repetitive work. Even simple automation rules (like auto-assigning or status updates) have a noticeable impact on efficiency.

Overall, Jira stands out because it combines flexibility, strong integrations, and intelligent automation to improve workflow and team collaboration in a very practical way. Review collected by and hosted on G2.com.

One of the main things I dislike about Jira is that the initial setup and customization can be overwhelming, especially for new users. While the flexibility is powerful, configuring workflows, permissions, and issue types often requires time and experience, which can slow down onboarding.

From a UI/UX perspective, the interface can feel cluttered at times, particularly when dealing with large projects or heavily customized boards. It’s not always intuitive to find certain settings, and this can impact productivity until you get used to it.

In terms of performance, Jira can occasionally become slow when handling very large datasets or complex filters, which affects the overall experience during peak usage.

Integrations are strong, but managing them can sometimes be tricky. For example, syncing with tools like GitHub or Slack may require additional configuration or troubleshooting to get everything working smoothly.

Regarding pricing and ROI, it might not be the most cost-effective option for small teams or startups, especially when adding multiple users or premium features. The cost can increase quickly as the team scales.

Support and onboarding are decent, but resolving specific or advanced issues sometimes depends heavily on documentation or community forums rather than direct support.

As for AI and intelligence, while there are some useful automation features, the AI capabilities still feel somewhat limited compared to what could be expected. More advanced insights or smarter recommendations could further improve productivity.

Overall, Jira is very powerful, but its complexity, occasional performance issues, and pricing structure can be challenging depending on the team size and experience level. Review collected by and hosted on G2.com.

Jira is an excellent tool for company-wide project management. We have a large product and engineering team, and it’s been great for managing work, tracking dependencies, and coordinating across multiple teams and spaces. Smaller improvements - like inline editing and the ability to add epics directly from the backlog view - have also made using Jira much faster and more seamless day to day. Review collected by and hosted on G2.com.

Jira has so many features and capabilities that it isn’t always straightforward or clear (a) where to access them and (b) what’s available or how to set things up. I’ve been using Jira for about six years now, and I still sometimes struggle to get to what I need; it can take me a minute or two to find the right place and figure it out. Review collected by and hosted on G2.com.

Jira is an outstanding tool for QA and development teams. The customizable workflows allow me to create tailored defect management processes that match our testing lifecycle. I particularly appreciate the ability to create custom issue types for bugs, test cases, and improvement tickets. The sprint board and backlog management make it easy to prioritize testing tasks, and the integration with tools like Selenium and CI/CD pipelines streamlines our automation workflows. The JQL (Jira Query Language) is extremely powerful for filtering and reporting on test coverage and defect metrics. Bulk editing and linking related issues saves significant time during regression cycles. Review collected by and hosted on G2.com.

The performance can be sluggish when dealing with large projects that have thousands of issues. Page load times for complex dashboards and filters can be frustrating during busy sprint periods. The configuration complexity is steep - setting up advanced workflows, permission schemes, and notification schemes requires significant admin expertise. The pricing model has also become increasingly expensive, especially for smaller teams. Additionally, the mobile app lacks many features available in the desktop version, making it difficult to manage tickets on the go. Some of the new UI changes in the cloud version feel unintuitive compared to the server version. Review collected by and hosted on G2.com.

It creates a consistent rhythm for how work moves across teams. It makes it easy to break down large features into manageable tasks, which helps during planning and execution. I like how workflows can be tailored to match how teams actually operate instead of forcing a fixed structure.

The backlog grooming experience is strong, you can prioritize, reorder, and refine work without losing context.

Notifications and activity tracking keep everyone aware of updates without constant follow-ups. It works well for both short-term sprint work and long-term tracking of ongoing issues. Review collected by and hosted on G2.com.

Jira can feel cluttered if too many fields or customizations are added.

Navigation between boards, backlogs, and reports can sometimes feel slow. It takes time for new team members to get comfortable with the interface. Review collected by and hosted on G2.com.

Jira has provided our development team with full visibility of all the steps involved in the delivery of the software, including backlog grooming, to deployment, due to its sophisticated issue tracking and workflows that can be customized. The sprint planning and roadmap are also especially useful, with the ability to establish achievable timelines and monitor our progress against the objectives without having to use both tools. The close connectivity with the GitHub and Confluence has been a game changer and our code, documentation, and project management have been linked to each other in a single seamless ecosystem. Review collected by and hosted on G2.com.

The interface of Jira may seem crowded, particularly to new team members, who take a lot of time to be onboarded and learn to navigate and use Jira safely. Initial setup also can be overwhelming, as the number of configuration options and settings can be overwhelming, sometimes needing a dedicated administrator to handle permissions, workflows, and project structures efficiently. Review collected by and hosted on G2.com.

Very flexible to use. You can set it up to match how your team works—whether that’s Scrum, Kanban, or something custom. It’s also not just for developers; QA, product, and even non-technical teams can use it without much friction.

Tracks everything in one place. You can follow a task from start to finish—requirement → development → testing → release—which makes coordination a lot easier, especially on larger teams.

Works well with other tools. It integrates smoothly with tools like Git, CI/CD pipelines, and collaboration apps, so everything stays connected and up to date.

Useful reports and dashboards. Features like burndown charts, sprint reports, and dashboards help teams stay on track and make better decisions.

Great for managing both the small and large projects. Overall, it’s a strong tool when you need clear processes and reliable tracking at scale.

AI features : Integration with browserstack enables easy test case creation and execution using AI

Wast suport from the Jeera team. Review collected by and hosted on G2.com.

With large projects or lots of data, it can become slow or laggy.

Navigating between boards, filters, and issues isn’t always smooth, especially for non-technical users.

Setting up workflows, permissions, and fields can take time and effort. It’s easy to overcomplicate things if not managed well. Review collected by and hosted on G2.com.

Jira is a highly structured tool for managing development tasks and tracking progress, and I use it regularly to handle user stories, bugs, and day-to-day tasks.

Its ease of use improves over time. At first it can feel very detailed and a bit overwhelming, but once you get used to it, creating tickets, updating statuses, adding comments, and following progress becomes a consistent, systematic process.

One of Jira’s strongest points is the breadth of features available. It supports sprint planning, backlog management, workflows, dashboards, and reporting, which makes it a good fit for Agile teams that need clear visibility into ongoing work.

When it comes to integrations, Jira works very well with tools like Bitbucket and Confluence. Being able to link commits, pull requests, and documentation directly to tickets helps maintain clear traceability between development activity and the tasks being worked on.

I use Jira every day throughout the development cycle to track tasks, update progress, and manage work items. Review collected by and hosted on G2.com.

From an implementation standpoint, the initial setup and configuration can be fairly complex. Setting up workflows, permissions, and project structures takes upfront planning and, in some cases, help from an admin.

The interface can also feel a bit heavy, particularly when you’re switching between multiple boards, filters, or reports.

When it comes to customer support, the documentation and community resources are solid, but the experience with direct support can vary depending on the plan.

For smaller teams, Jira can sometimes feel too detailed if you only need straightforward task tracking. Review collected by and hosted on G2.com.

I like Jira because it keeps work organized and easy to follow. The UI is clean once you get used to it, and it’s simple to track tasks and progress. It also connects well with other tools we use, which makes things more convenient.

In terms of performance, it’s generally reliable and handles projects well, even with bigger teams. Pricing can feel a bit high depending on the plan, but it’s worth it for the value you get, especially if your team uses it daily.

The onboarding can take some time at first, but there’s good support and plenty of resources to help you figure things out. I also like the automation and AI features—they help save time on repetitive tasks and give useful insights.

Overall, it’s a solid tool for managing projects and keeping everyone on the same page. Review collected by and hosted on G2.com.

One thing I don’t like about Jira is that it can feel a bit complicated at first. The setup and navigation aren’t always very intuitive, especially for new users. Sometimes it feels like there are too many options for simple tasks.

It can also be a bit slow at times, and the pricing can add up depending on the features you need. Overall, it’s a powerful tool, but there’s definitely a learning curve. Review collected by and hosted on G2.com.

A tool that allows structuring teamwork and properly distributing tasks among different teams. It facilitates collaboration both with internal members and with clients or other external people. The kanban is a real advantage for us in its use because it makes tracking clearer and simpler on a daily basis. Review collected by and hosted on G2.com.

The use of Swimlanes is sometimes complicated when you want to set priorities that don't necessarily correspond to the columns. It takes a little time to get the hang of it and especially to clearly explain to the teams how to bring a topic up in the priorities, since it's not always possible to do it simply via drag and drop. Review collected by and hosted on G2.com.