Jira
AtlassianReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
7,248 reviews
from
External reviews are not included in the AWS star rating for the product.
Effective Task Management with Room for Improvement
What do you like best about the product?
I use Jira for daily effort tracking and task management. I appreciate the easy tracking of stories and tasks. I like its feature management, especially the ability to break features into tasks. We can also create stories for sprints, which is helpful. Logging our efforts daily and adding comments is another feature I value. The initial setup was easy.
What do you dislike about the product?
Jira is pricier than Azure DevOps and it could offer more advantages. It would be beneficial if it had CiCD capabilities.
What problems is the product solving and how is that benefiting you?
I use Jira for daily effort tracking and task management. It helps me easily track stories and tasks, manage features by breaking them into tasks, and create stories for sprints.
Jira Makes Client Ticket Tracking Clear and Efficient.
What do you like best about the product?
Jira is generally employed to monitor client service tickets. It enables the tracking of client requests and ensures that the correct teams handle the requests in the due course. Moreover, the status allows the teams to get a good overview of what is in progress, what is pending, etc., which is essential during client reviews.
What do you dislike about the product?
The learning curve may be quite steep for new team members who are not familiar with organized ticketing systems.
What problems is the product solving and how is that benefiting you?
Previously, client issues were being handled through email chains, which was difficult. However, the use of Jira has made things quite clear since the issues are being handled through a ticketing system, especially during service audits.
Jira Keeps Cross-Functional Tickets Moving and Bottlenecks Visible.
What do you like best about the product?
Jira is primarily used to manage process tickets and track cross-functional dependencies. I make use of stages to monitor the movement of tasks, ensuring timely identification of bottlenecks. It helps to avoid situations where tickets wait pending assignment. Moreover, custom fields can be used while tracking operation issues for report generation purposes.
What do you dislike about the product?
However, the interface may appear complicated for non-technical users, especially when they are setting up their dashboards.
What problems is the product solving and how is that benefiting you?
Previously, prior to Jira, the manner in which business requests were monitored or tracked using email conversations and shared spreadsheets did not allow for the necessary prioritization of the same.
Great Visibility and Dashboards for Tracking Tasks in Jira
What do you like best about the product?
Jira is mainly used to monitor operational tasks and internal process requests. I mostly use Jira to record tickets and monitor the progress of tasks. Jira provides good visibility to minimize reliance on email threads to understand where to go. Jira dashboards are helpful to get a quick overview of tasks and priorities.
What do you dislike about the product?
Nevertheless, if the tasks are not regularly updated, the board can become outdated very quickly, making it irrelevant. It relies largely on the regular usage of the tasks by the team.
What problems is the product solving and how is that benefiting you?
In the past, the operations tasks were being handled by emails and spreadsheets. This makes it quite difficult to track the progress. A structured process was created by Jira that enhanced accountability.
Automation Powerhouse, but Complex Configuration
What do you like best about the product?
I love the automation in Jira as it removes human error and makes sure no work gets stuck because someone forgot to click a button. This automation is really helpful when tasks automatically move from 'In Progress' to 'Ready for Testing' upon completion, which ensures smooth workflow. I appreciate Jira's stability and traceability, as it acts like a 'long-term memory' for my development team, preventing regression. The initial setup of Jira is fast and simple, taking less than 10 minutes with pre-built Scrum or Kanban templates, allowing teams to get started quickly without needing an expert. I also find value in using Team-Managed Spaces, which give individual teams the power to control settings without the need for a professional Jira Administrator. Furthermore, integrating Jira with Slack is beneficial as it avoids the need to constantly check Jira by providing notifications directly in Slack, and allows tasks to be managed right from Slack messages.
What do you dislike about the product?
While Jira is a powerhouse, it’s far from perfect. There are several areas that could be significantly improved. One issue is the 'Configuration Trap' due to its complexity. Jira is so customizable that it’s easy to over-engineer it. The problem is that many teams create 'subway map' workflows with 15 different steps just to finish one task, which leads to clutter and slows down actual progress. Another complaint is that Jira feels more like a tool for managers than for the people actually doing the work, as it requires manual updates. If an engineer fixes a bug and forgets to update the status in Jira, the data becomes 'lying data', which worries project managers even though the work is actually finished.
What problems is the product solving and how is that benefiting you?
I use Jira to manage software development sprints, ensuring no bug is forgotten and fixes are tested. Its automation reduces human error and prevents work from getting stuck. It serves as a long-term memory for the team, preventing regression.
Easy Task Assignment and Completion Tracking
What do you like best about the product?
The assigning of task to team members and tracking the completion is very easy..
What do you dislike about the product?
There are so many options which is at times confusing to select a template based on your team structure
What problems is the product solving and how is that benefiting you?
It helps me track progress of my project and decide on how can my goals be achieved
Effortless Task Tracking and Ownership Clarity
What do you like best about the product?
I use Jira to quickly monitor and track daily tasks, progress, and tickets all in one place. It’s especially helpful for creating tickets for fixes and corrections or flagging bugs, which reduces confusion around ownership and makes it clear who is handling what. Having everything in a single location also means I don’t have to deal with multiple scattered platforms.
The comments are the most useful feature for me because they provide updates and make it easy to have small, focused discussions. When a task gets stuck, the comments are where we can talk through delays, clarify any confusion, and keep everyone aligned on what’s happening.
The comments are the most useful feature for me because they provide updates and make it easy to have small, focused discussions. When a task gets stuck, the comments are where we can talk through delays, clarify any confusion, and keep everyone aligned on what’s happening.
What do you dislike about the product?
It is a bit complex for a new user but then with time use to it.
What problems is the product solving and how is that benefiting you?
I use Jira to monitor daily tasks and track progress in one place. It solves ownership clarity issues and centralizes communication, reducing platform clutter. Comments are very helpful for updates and minor task discussions, especially when issues arise.
Flexible Workflows and Powerful Traceability That Scale with Your Team
What do you like best about the product?
I like Jira most for its flexible workflows, powerful issue tracking, and strong traceability. It adapts to complex team processes, scales well from small projects to enterprises, and integrates with development tools, making planning, execution, and reporting structured and transparent.
What do you dislike about the product?
I dislike Jira’s complexity, slow performance at scale, and heavy configuration overhead. Simple tasks can feel bloated, the interface overwhelms new users, and maintaining workflows, permissions, and automations often requires dedicated administration, which reduces agility for smaller teams significantly today.
What problems is the product solving and how is that benefiting you?
Jira solves problems of task visibility, coordination, and accountability in complex projects. It centralizes work, tracks progress, manages dependencies, and enforces workflows. This benefits me by improving transparency, prioritization, and delivery predictability, especially when collaborating across teams, roles, and timelines.
Jira Keeps Tasks, Bugs, and Progress Perfectly Aligned
What do you like best about the product?
Jira is very effective for tracking tasks, bugs, and project progress in one place. It provides clear visibility into work status, priorities, and ownership, which helps teams stay aligned. The flexibility to customize workflows and dashboards makes it suitable for different team needs.
What do you dislike about the product?
Jira can feel complex at first, especially for new users. Some features and configurations take time to understand, and setup can be heavy if workflows are not defined clearly.
What problems is the product solving and how is that benefiting you?
Jira helps solve the challenge of managing projects, tracking bugs, and coordinating work across teams in one place. It improves visibility into tasks, priorities, and progress, making it easier to plan work and track issues from start to finish. This helps teams stay aligned, reduces miscommunication, and improves overall delivery efficiency.
Jira helped me manage a complex roadmap!
What do you like best about the product?
Jira helped me manage the roadmap of major clients in a practical way.
What do you dislike about the product?
Usability at first may seem complex, but it is possible to adapt quickly by using Agile practices.
What problems is the product solving and how is that benefiting you?
Jira helped us have a clear roadmap of what we need to evolve in our software and also to understand the feature priorities for our clients.
showing 41 - 50