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 asset 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 do not 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 subject up in the priorities, since it is not always possible to do so simply via drag and drop. Review collected by and hosted on G2.com.

What I like best about Jira is its ability to organize and track work efficiently in one place. It makes it easy to create, prioritize, and assign tasks, monitor progress through Scrum or Kanban boards, and collaborate with team members. I also appreciate its integration with tools like Bitbucket and Confluence, which helps streamline development, testing, and documentation workflows. Overall, Jira provides good visibility into project status and improves team coordination. Review collected by and hosted on G2.com.

One thing I dislike about Jira is that it can feel overwhelming at first because of its many features and configuration options. Creating or navigating complex workflows can take time, and finding specific information can sometimes require several clicks. However, once the project is set up well and you're familiar with the interface, it becomes much easier to use. Review collected by and hosted on G2.com.

What I like most about Jira is that it centralizes task management, facilitates collaboration between teams, and allows for clear and organized tracking of project progress. Review collected by and hosted on G2.com.

What I like least about Jira is that it can be complex at first, it requires time to set it up correctly, and if the project is not well organized, navigating and tracking tasks can become confusing. Review collected by and hosted on G2.com.

I like how Jira lets you have different projects on the go at once. The dashboards functionality makes it easy to see what tickets you have open and which are awaiting your comments or input. This really helps keep things organized when you have multiple teams and departments working on various projects at the same time. The initial setup of Jira was seamless, and I didn't run into any issues. I also appreciate that you can add watchers to tickets so that it's not all on one person to follow up, which my manager uses to keep the IT team on track. Review collected by and hosted on G2.com.

Sometimes I find it hard to find which tickets I've submitted that are still open. I can see my recent tickets which include old ones that have been closed for a while. It would be useful to have a specific section for my tickets that are open. Review collected by and hosted on G2.com.

What I most like about jira is the way it is structure and makes everything feel completely rigid once you get used to it. I like the ability of customization - you can adapt to different types of projects. Integrations like Slack and github makes it easier to stay aligned where we work and team remains in flow with whats going on at a glance. Review collected by and hosted on G2.com.

When I’m working on large-scale projects, it can sometimes feel a bit slow, especially when loading boards. Overall, it’s a powerful tool, but the experience of getting used to managing large-scale projects could be smoother. Review collected by and hosted on G2.com.