Jira has helped our team manage internal sales requests and customer related tasks more efficiently, we use it to coordinate activities between sales, implementation , support and operations, ensuring that every request has clear ownership and a defined timeline, it has brought much more structure to our post sales and pre sales processes., the ability to track every task from creation to completion, whether its preparing customer documentation, coordinating product demos, requesting pricing approvals, or following on implementation activities, Jira provides complete visibility into the status of each request, the customizable workflow also ensure that nothing progresses without the necessary approvals. the dashboards and kanban boards makes it easy to monitor pending work and identify bottlenecks, mentions , comment and attachment keep all communication related to a tasks in one place, reducing unnecessary email exchanges. Jira integrates effectively with, agentforce sales , Google workspace, communication platform ,documentation tools, these integration help connect customer information with internal executions workflows, Jira has improved collaboration between sales, support , finance and implementation teams by providing a transparent workflow for customer related activities. Review collected by and hosted on G2.com.

i dislike about jira is that simple operational tasks can sometimes require more ticket fields and workflow steps than necessary which slow down quick internal requests, during busy sales periods, navigating heavily customized project with numerous issues types can also make it harder to locate the right information quickly, while jira is highly flexible and powerful, simplifying routine workflows and reducing unnecessary administrative steps would make it even more efficient for supporting day to day sales operations. Review collected by and hosted on G2.com.

The most helpful thing about Jira is that it’s user-friendly and clearly lays out exactly what’s needed to log a bug for tracking purposes. It also integrates easily with Zendesk and Slack, and it offers alerts when there are any updates to the reported bug. It also helps summarise with their AI offering making it easy to note all the necessary details. I feel like the company is getting their monies worth as it centralises all the data saved in the bug and saving as it is a larger corporation. Onboarding was very swift and took less than an hour and the speed is almost instant when logging a bug. Review collected by and hosted on G2.com.

I’d say Jira’s biggest downside is that it can be overly complex. It’s very customisable, which is useful, but if it isn’t configured well, you can end up with too many fields, statuses, and workflows. That can slow teams down rather than help them. Review collected by and hosted on G2.com.

I have been using Jira extensively for around 4.6 years across my BA and Product Owner responsibilities. What I particularly like about Jira is that it is very intuitive and easy to use, while still providing powerful features for managing complex projects. I have used it for creating and managing epics, user stories, tasks and bugs, maintaining and prioritizing the product backlog, sprint planning, tracking sprint progress, and managing releases.

One of the biggest advantages I find in Jira is the transparency it provides across teams. Everyone can clearly see what is planned, what is in progress, what is blocked, and what has been completed. I also find its reporting and dashboards useful for tracking sprint performance and team progress.

Another strong feature is its integration capability. Jira can integrate with tools like Slack, Confluence, GitHub and other collaboration or development tools, which reduces manual communication and keeps information synchronized. Overall, after using Jira for 4.6 years, I see it not just as a ticketing tool, but as a central platform for managing requirements, Agile delivery, collaboration, and product development. Review collected by and hosted on G2.com.

One thing I would improve about Jira is the consistency of its UI. I have been using Jira for around 4.6 years, so I am very familiar with the interface. However, Jira frequently introduces small UI changes. Although these changes are generally intended to improve the product, sometimes they move or redesign elements that we use every day, which temporarily affects productivity because we have to look for familiar modules again.

I also feel the Bulk Update functionality could be more powerful, particularly when dealing with large numbers of issues or when different values need to be applied to different issues.

Another area is customization. Jira's flexibility is one of its biggest strengths, but it can also become a weakness when projects have overly complex workflows, too many fields, or inconsistent configurations. Similarly, advanced features like JQL are extremely powerful but have a learning curve for new users. Review collected by and hosted on G2.com.

I like Jira because it helps keep all tasks, bugs, and requirements in one place, making it easier to track the status and progress of the work. It really helps team communication and follow-up on issues. What I really like most about Jira is how easy it is to track tasks and bugs, and have clear visibility of ticket status and progress. It is easy to use and makes it easier for the team to follow up. Also, the visibility is very good and clear; it’s like an open book for everyone to see the things that are happening. The initial setup was really easy too, with an easy process to set it up after receiving a mail from our PMO, allowing us to see our team members and our project without many difficulties once everything was configured. Review collected by and hosted on G2.com.

Sometimes when there are a lot of tickets, Jira seems to work somewhat slow. Also, notifications can sometimes become too frequent, which can be a bit overwhelming. Review collected by and hosted on G2.com.

Project management and tracking

Productivity and blocker tracking and discussion

Requirement discussion with business

and Agile process to be on top of SDLC model Review collected by and hosted on G2.com.

Reporting takes manual effort. Sprint and velocity reports don’t show individual contribution or completion clearly, so my team ends up rebuilding them in Calude by integrating JIRA for leadership reviews. Review collected by and hosted on G2.com.

Fully supports Agile methodologies (Scrum/Kanban).

Highly customizable workflows.

Centralized task and bug tracking.

Integrates with thousands of developer apps (GitHub, Slack, etc.).

Comprehensive project analytics and reporting.

Built-in automation for repetitive tasks.

Scales easily from small teams to large enterprises.

UI/UX: Highly customizable dashboards with comprehensive and detailed task views.

Pricing: Free for up to 10 users with a flexible, pay-per-user scaling model.

After-sales Support: Extensive documentation, an active global community forum, and 24/7 technical support for premium plans. Review collected by and hosted on G2.com.

UI/UX: The interface can be cluttered and overwhelming (steep learning curve), especially for non-technical users or beginners.

Setup: Requires significant time, effort, and often a dedicated admin to properly configure workflows for the team.

Pricing: Subscription costs scale up quickly as the team grows, and many essential features require purchasing expensive third-party plugins.

Performance: The system can become slow or laggy when handling a massive amount of data or running too many integrations/add-ons. Review collected by and hosted on G2.com.

I am a project manager and Jira has completely transformed how I manage project quality. I can enforce process compliance without slowing anyone down. It has helped me in reducing bugs escaping to production. It has elevated the quality of our work with its powerful issues tracking, highly customizable workflows, and strong support for agile methodologies. Our team has integrated Jira seamlessly with our Salesforce CRM, helping in robust reporting and dashboards. Fits best for our DevOps, Dev, and QA team. Review collected by and hosted on G2.com.

Couple of more features like Zephyr squad and other premium features should be made available for free of cost instead of charging. Also setting up sophisticated workflows and additional permissions might be overwhelming, takes a lot of time and requires technical expertise. Review collected by and hosted on G2.com.

I appreciate Jira's exceptional flexibility in adapting to diverse team needs. I love the customizable workflows, allowing teams to tailor workflows to match their exact processes, whether using Scrum, Kanban, or other methodologies. I find the granular tracking and visibility helpful, providing comprehensive visibility into development cycles by allowing users to create, assign, and track issues at a detailed level in real-time. The powerful integrations stand out for me, as Jira connects seamlessly with essential tools like GitHub, Bitbucket, and Slack, fostering a unified DevOps ecosystem. Additionally, I found the initial setup of Jira easy and better compared to other platforms. Beyond the core features, the built-in AI and smart automation features significantly cut down our manual scheduling and routine triaging tasks. Considering the sheer amount of time saved across our engineering and product teams, Jira delivers an outstanding return on investment (ROI) that easily justifies its pricing. Review collected by and hosted on G2.com.

Based on common user experiences, here are some areas where Jira is often cited as falling short: Steep Learning Curve: New users often find the interface complex and difficult to navigate, requiring significant training to use effectively. Workflow Complexity: The high level of customization can lead to bloated, over-engineered workflows that are hard to manage and maintain over time. Performance Issues: Some users report that the platform can feel sluggish, bloated, or slow, particularly when managing large projects. Review collected by and hosted on G2.com.

The board view is what I use most. The whole team can see what's in progress, what's blocked and who owns what, so we need fewer status meetings. Saved filters in JQL are a close second, since pulling a list for a stand-up or report takes seconds. Having comments, attachments and linked tickets on each task also means the history is still there months later when someone asks why we did something. Review collected by and hosted on G2.com.

The setup can get complicated fast. Workflows, custom fields and permissions take real effort to configure, and it's easy to end up with a messy project if nobody owns it. Search and JQL have a learning curve for new users, and the interface can feel slow and cluttered on large projects with lots of tickets. Notifications also get noisy unless you tune them. Review collected by and hosted on G2.com.

Jira acts as the ultimate source of truth for complex projects. By centralizing tasks, automating updates, and providing clear visual tracking, it prevents communication gaps and reduces micromanagement. Ultimately, it brings structure to team collaboration and delivers a genuinely satisfying sense of progress when crossing the finish line. Review collected by and hosted on G2.com.

When it’s misused, Jira can shift from a collaboration tool into a surveillance tool. It’s far too easy for stakeholders to fixate on velocity charts, burndown metrics, and time-tracking data, then use those numbers to micromanage developers instead of focusing on the real value being delivered. Review collected by and hosted on G2.com.