Jira
AtlassianReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
7,437 reviews
from
External reviews are not included in the AWS star rating for the product.
Seamless Slack Integration with Jira Boosts Productivity
What do you like best about the product?
I like how Jira integrates with Slack seamlessly, which eliminates the need to constantly check emails for assigned tickets, as I can now see them on Slack. I also appreciate that it helps in tracking tickets by allowing assignment with deadlines, which prevents any problems from going missing. Furthermore, setting up Jira was very easy, despite taking some time because we had to create multiple boards and epics.
What do you dislike about the product?
I need to copy the ticket link for the GitHub PRs, then I need to open that ticket. There is no button to copy the ticket link on the icon of the ticket. First, there must be a link copy to clipboard function in the ticket icon. Second, the ticket should be directly assigned to the current sprint as the ticket is created, but it doesn't.
What problems is the product solving and how is that benefiting you?
Jira helps track client issues with deadlines, preventing them from getting lost or forgotten. Its seamless integration with Slack lets me see assigned tickets without checking emails, streamlining my workflow.
Jira Makes Fair Task Distribution Easy Across the Team.
What do you like best about the product?
Jira has proven itself an effective method of distributing tasks among team members without the risk of overloading one particular person. In order to make sure that tasks are distributed fairly among my team members, I often turn to Jira to find out who is supposed to do what, and then redistribute tasks accordingly in order to ensure balance in workload.
What do you dislike about the product?
Reassignment of several tickets might not always be easy, especially in comparison with changing the assignee of just one ticket, but the results will definitely be worth the trouble.
What problems is the product solving and how is that benefiting you?
The greatest advantage of using Jira for managing projects is the possibility of distributing tasks and workload in a way that will be as fair to all team members as possible.
A Solid Ticketing System for Managing CMS Development Workflows
What do you like best about the product?
What we value most about Jira is how clearly it helps us structure and manage technical requests in a traceable way. We use it as our central ticketing system to report bugs, request improvements, and communicate with both our internal tech team and the developers of our CMS.
Jira lets us follow the entire lifecycle of each ticket—from creation through to resolution—across different statuses such as open, in progress, pending QA, or awaiting feedback from our side. Having this level of visibility makes coordination between the editorial, product, and development teams smoother, so nothing gets overlooked and priorities remain clearly defined.
Jira lets us follow the entire lifecycle of each ticket—from creation through to resolution—across different statuses such as open, in progress, pending QA, or awaiting feedback from our side. Having this level of visibility makes coordination between the editorial, product, and development teams smoother, so nothing gets overlooked and priorities remain clearly defined.
What do you dislike about the product?
One of Jira’s main drawbacks is that it can feel complex and not very intuitive for non-technical users, especially in a newsroom environment where not everyone is accustomed to working with development tools.
The interface and workflow configuration can be overwhelming at first, and even simple tasks can take more steps than you’d expect. For editorial teams, this can slow adoption, create friction in day-to-day use, and ultimately make Jira feel less user-friendly than simpler ticketing or communication tools.
The interface and workflow configuration can be overwhelming at first, and even simple tasks can take more steps than you’d expect. For editorial teams, this can slow adoption, create friction in day-to-day use, and ultimately make Jira feel less user-friendly than simpler ticketing or communication tools.
What problems is the product solving and how is that benefiting you?
Before we started using Jira, managing technical requests felt fragmented. We often relied on emails or informal communication, which made it difficult to clearly track progress, ownership, and responsibilities.
Jira addresses this by giving us a centralized, structured way to handle all technical requests in one place. We can easily see which tickets are open, which are resolved, which are pending quality control, and which ones still require additional input from our side.
As a result, we’re better organized, communication with developers is smoother, and there’s more transparency across teams. It also makes it easier to prioritize work and ensures that improvements and bug fixes are consistently followed up until they’re fully completed.
Jira addresses this by giving us a centralized, structured way to handle all technical requests in one place. We can easily see which tickets are open, which are resolved, which are pending quality control, and which ones still require additional input from our side.
As a result, we’re better organized, communication with developers is smoother, and there’s more transparency across teams. It also makes it easier to prioritize work and ensures that improvements and bug fixes are consistently followed up until they’re fully completed.
Jira Makes Prioritizing and Managing Requests Effortless.
What do you like best about the product?
Jira comes handy where there are many requests and it is necessary to establish which requests should be dealt with first. I normally use Jira to organize requests by prioritization and urgency in order to concentrate on what is really important and not just attend to all the requests coming in.
What do you dislike about the product?
It could be quite tiring to keep on changing priorities when several other requests are being worked on at once.
What problems is the product solving and how is that benefiting you?
What is important about it is that it makes decision making much easier since everything is listed out.
Great for Tracking Ticket History and Chains of Events.
What do you like best about the product?
Jira becomes particularly handy when one needs to find out who was performing certain actions and when these actions took place. I tend to use it quite often for mapping the chain of events for a ticket, instead of analyzing its status.
What do you dislike about the product?
Sometimes, during ticket duplication, some unnecessary information can be included that will have to be removed manually later.
What problems is the product solving and how is that benefiting you?
What is most important, there is an excellent traceability feature. Every change, update, or any other activity performed is saved, thus, making any subsequent check more reliable.
Flexible Issue Tracking with Powerful Workflows and Integrations
What do you like best about the product?
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.
What do you dislike about the product?
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
What problems is the product solving and how is that benefiting you?
Prioritisation by aligning backlogs and issue ranking helps teams focus on most important work instead of reacting randomly. Boards, sprint reports and dashboards make it easier to see whether work is on track. clear ownership and status changes make it obvious who is repsonsible what and where things are stuck. Linking commits, pull requests and deployments to issue connect planning with actual code changes
The Ultimate Task and Issue Tracker with Powerful Customization and Automation
What do you like best about the product?
The ultimate tool to keep track of all types of tasks and issues, vast customization and automation possibilities.
What do you dislike about the product?
It may feel too complex especially for new users.
What problems is the product solving and how is that benefiting you?
It solves the problem of tracking work across teams and projects. It organizes tasks, bugs, and feature requests, provides visibility into progress, and helps enforce workflows and accountability.
Great for Recording and Monitoring Live Issues and Escalations
What do you like best about the product?
A great tool to record and monitor live issues, escalations, and other events.
What do you dislike about the product?
I don't know the full scale of what it's capable of; it's a very 'tech-exclusive' tool, despite the fact that I have access to its platform.
What problems is the product solving and how is that benefiting you?
Currently being used to record and monitor escalations based on a custom workflow we designed; also used to submit and track issues.
Flexible, Transparent Work Tracking Across Teams with Jira
What do you like best about the product?
What I like most about Jira is how flexible and transparent it is for tracking work from start to finish, especially in complex, cross-functional environments.
Jira serves as a single, centralized source of truth where tasks, issues, and workflows are clearly documented and visible to all stakeholders. Its ability to customize workflows, issue types, and fields makes it easy to adapt across different teams—whether it’s security, development, operations, or compliance—without forcing everyone into a one-size-fits-all process.
Jira serves as a single, centralized source of truth where tasks, issues, and workflows are clearly documented and visible to all stakeholders. Its ability to customize workflows, issue types, and fields makes it easy to adapt across different teams—whether it’s security, development, operations, or compliance—without forcing everyone into a one-size-fits-all process.
What do you dislike about the product?
While Jira is a powerful and flexible tool, there are a few aspects that can be challenging, especially in large or operationally heavy environments. First, its complexity can create a steep learning curve for new users and teams. Second, the ability to customize almost everything can sometimes lead to over-customization, which adds process overhead and makes workflows harder to maintain. Finally, without add-ons, Jira’s native reporting can feel limited, particularly when you need more detailed or tailored insights.
What problems is the product solving and how is that benefiting you?
Jira addresses the core challenge of managing, tracking, and coordinating work in complex environments where multiple teams, priorities, and deadlines overlap. Without a structured system in place, work can easily become fragmented across emails, chats, and spreadsheets, which leads to missed follow-ups, unclear ownership, and reduced accountability.
Visual and Useful, but Complex Setup
What do you like best about the product?
I really like the amount of visual and easy-to-use tools that Jira offers to organize work and document tasks.
What do you dislike about the product?
Sometimes the configuration of visual aspects or setting certain rules in tasks is a bit complex. And in the initial integration, we turned to a consultancy that did the basic setup for us to start working.
What problems is the product solving and how is that benefiting you?
Jira helps us have a global view of tasks, prioritize them, distribute them among teams, and maintain communication, which streamlines teamwork.
showing 81 - 90