Jira Reviews & Product Details

Jira works well as a ticketing and bug-tracking tool. Our team can collaborate easily on issues and project work. It also provides excellent dashboards that give quick insight into the status of tasks and projects. It’s simple to comment on tickets, change the status or assignee, and close them, and it’s just as easy to open new tickets when needed. I also like that you can follow issues to receive notifications and emails whenever someone updates them, and you can “star” issues to keep a closer watch on the ones that matter most. Implementing Jira is quick and easy from the start. Migrating from another ticketing system would likely be more difficult. I use Jira daily. It's also easy to integrate with Confluence for documentation. Review collected by and hosted on G2.com.

Jira doesn’t support SSO unless you pay for a more expensive license. In my view, vendors shouldn’t charge extra for SSO or MFA, since these are basic yet critical security features. Review collected by and hosted on G2.com.

Jira helps me keep my tasks properly tracked and manage tickets and other work items. It also helps me design a clear workflow, like understanding the current status of my task and how much time it takes to complete. Since my team is connected in Jira, we can work together smoothly, and my manager can easily assign any task to me. It also helps the client keep proper track of the project. Review collected by and hosted on G2.com.

Sometimes, when there are too many tickets and everything feels overloaded, it becomes difficult for me to manage my tasks. I get confused about which ticket is the current one, and tracking tickets date-wise also seems complicated to me. Also, having different workflows for different projects is frustrating sometimes. Review collected by and hosted on G2.com.

What I appreciate most about Jira is how well it helps organise and track work in a team environment. In my corporate workflow we use it to manage tasks, bug reports and sprint planning for ongoing projects. The ease of use become clear once the team gets familiar with the interface and the ease of implementation was manageable when our team first introduced it for project tracking. Jira also offers a strong number of feature including task boards, sprint tracking, reporting tools and workflow customisation. My frequency of use is daily because I rely on it to update task progress and monitor project status. The ease of integration with development tools, communication platforms and documentation systems also makes it very practical. When questions come up the available guides and customer support resources are helpful. Review collected by and hosted on G2.com.

One drawback is that the interface can feel slightly complex for new users especially when dealing with multiple workflows or project boards. It sometimes takes a bit of time for team members to fully understand how everything works. Review collected by and hosted on G2.com.

I like how customizable Jira is, as it has made it easier for us to create different workspaces for different teams without having to compromise on our specific needs. The built-in security functions are also appreciated, as Jira supports the latest security protocols like RBAC, SSO, and SCIM. Review collected by and hosted on G2.com.

The search function is borderline useless. Our previous system allowed us to find things based on keywords, but now we basically have to know the ticket number to find the previous tickets. Despite its customizability, I wish it could present a more simplified view for teams that don't need every box checked. The initial setup was also bad because we did it ourselves. Review collected by and hosted on G2.com.

Organizing your work and todos in a team is obviously the best aspect about Jira. I wouldn't know how to properly do that without it. Review collected by and hosted on G2.com.

At times, Jira can feel a bit cumbersome to use, especially when I’m trying to access certain features or actions. Some of these options are placed in spots where I wouldn’t expect to find them, and the layout can feel inconsistent from one area to another. Review collected by and hosted on G2.com.

Jira helps me alot in managing infrastructure tasks, deployment activites, and issue tracking with the development team, one thing i really like is how clearly we can track work through ticket, every task like server setup, CI/CD pipeline updates, or deployment fixes can be created as a Jira issue and assigned properly.. Jira boards are also very helpful during sprint cycles,. even though work is sometimes operational and urgent, we still manage tasks through sprint boards so the whole team can see the progress, it improves transparency between DevOps and developers. i also like it integration support ,we connect jira with our repositories, and deployment tools so that commits and deployments can be linked with tickets. the search filter and dashboards are also useful. it our important tool of daily workflow. Review collected by and hosted on G2.com.

sometime it can feel a little heavy for simple tasks, for quick operational work, creating and updating tickets may take extra time , also the UI can be slightly confusing for new team members who are not familiar with the workflow.. also there is small issue is that configuring workflows or automation rules sometimes, requires admin support which slows down small changes. Review collected by and hosted on G2.com.

JQL (Jira Query Language) is an ultimate search tool. It lets you run precise queries to find exactly what you need across thousands of issues, which makes data reporting incredibly granular.

Deep traceability links the entire development lifecycle. You can follow a single task from the initial requirement all the way to the specific line of code and the final deployment.

Robust automation, with its "if-this-then-that" engine, cuts down on manual "busy work." It can automatically assign tickets, keep parent/child statuses in sync, and trigger alerts based on specific logic.

For enterprise scaling, features like Advanced Roadmaps help leadership see how dozens of different teams are tracking toward a single goal, and they make dependencies visible before they turn into blockers. Review collected by and hosted on G2.com.

Jira is only as good as its admin. Its biggest strength—nearly endless customization—can quickly turn into its biggest weakness when the setup is over-engineered. Review collected by and hosted on G2.com.

Jira is a great tool for managing tasks and tracking project progress. It helps teams organize their work clearly using tickets, boards, and workflows. I like how easy it is to assign tasks, monitor status, and collaborate with team members. The dashboards and reporting features also help in understanding project progress and identifying issues quickly. It works well for teams that follow Agile or structured project management processes. Review collected by and hosted on G2.com.

One downside of Jira is that it can be a bit complicated for new users. The interface has many features, which sometimes makes it difficult to navigate at first. Setting up workflows or configurations may also require some technical understanding. If the user interface was a bit simpler and easier for beginners, it would improve the overall experience. Review collected by and hosted on G2.com.

Everything appears in a single pane which avoids confusion and helps track all updates in one place. There are no side tickets or scattered threads, so the entire discussion, attachments, and activity history remain visible within the same ticket. This makes it much easier to understand the full context of an issue without searching across multiple threads.

Re assigning ticket is very simple and quick. If a request reaches the wrong team or requires additional expertise, it can be reassigned within seconds. This ensures requests reach the correct owner faster and prevents delays in resolution.

The priority levels such as Low, Medium, and Critical make it easier for the product or engineering team to identify urgent requests. This structured prioritization helps teams quickly separate operational issues from normal feature requests and address time sensitive matters more efficiently.

The ability to paste images directly into tickets is extremely convenient. Screenshots of errors, dashboards, or logs can be shared instantly. This helps explain issues clearly and allows technical teams to diagnose problems faster without requiring lengthy explanations.

The workflow visibility is very strong. Each ticket clearly shows its status, owner, priority, and activity history. This transparency helps teams understand exactly where a request is in the process and reduces the need for frequent follow ups.

The comment and tagging system improves collaboration across teams. Team members can mention specific individuals so the right stakeholders review the issue. This keeps discussions centralized within the ticket instead of scattered across emails or chats.

The search and filtering capabilities make it easy to locate past tickets, track similar issues, and review historical resolutions. This helps teams quickly reference previous work and avoid duplicate investigations.

Ease of implementation is another strong point. The platform allows teams to start using structured ticket management quickly with configurable workflows, custom fields, and permission settings. Organizations can adapt the system to their operational process without needing heavy development effort.

Customer support resources and documentation are very helpful. The support materials, guides, and community forums provide clear explanations for common configuration or workflow questions, making it easier for teams to troubleshoot and optimize usage.

The platform is used frequently throughout the workday because it becomes the central place for tracking requests, reporting issues, and coordinating with product or engineering teams. Having a single operational hub significantly improves visibility and efficiency.

The dashboards and reporting features help teams monitor ticket volumes, response timelines, and recurring issues. This helps identify operational patterns and provides insights that can improve internal processes. Review collected by and hosted on G2.com.

One improvement that could make the platform even more effective is clearer and more descriptive ticket statuses. For example, statuses such as Almost Done, Pending Last Leg, Approval Needed from Tech Team or Senior Team, In Progress with Maker, or In Progress with Checker would provide better visibility into the exact stage of the task. This would help client service managers quickly understand progress and communicate accurate updates to clients without needing to review the entire ticket conversation.

The interface can sometimes feel overwhelming for new users because there are many fields, options, and configurations within a single ticket. This can make the learning curve slightly steep for teams that are using the platform for the first time.

Ticket forms can occasionally contain too many required fields depending on how the project is configured. This can slow down the process of raising a quick request, especially when the user only wants to report a simple issue.

Navigation between multiple projects or boards can take time to get used to. When several projects exist within the workspace, finding the correct queue or board may require additional filtering. Review collected by and hosted on G2.com.

It keeps all tasks neat and easy to find.

It’s simple to see what work is done and what is left.

It helps team members work together easily.

The boards can be changed the way you like.

It works well for small teams and big teams.

It gives helpful reports and dashboards to understand progress. Review collected by and hosted on G2.com.

The mobile app is not as smooth as the desktop version. Review collected by and hosted on G2.com.