Jira
AtlassianReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
7,108 reviews
from
External reviews are not included in the AWS star rating for the product.
Robust, Customizable, but Complex for New Users
What do you like best about the product?
I like Jira for its powerful project management features. Its highly customizable workflow allows me to adapt to any project, whether it's software development or general task management. The ability to create detailed user stories, assign tasks, and track progress is incredibly helpful for team collaboration. The integration with tools like Slack, GitHub, or Confluence streamlines our work across multiple platforms. Also, the real-time data on project progress and the useful reports and dashboards help in making informed decisions.
What do you dislike about the product?
Jira has a steep learning curve, especially for new users, making it overwhelming to navigate. The onboarding process could be more intuitive with better tutorials. There are performance issues when handling large projects, causing Jira to become slow. The customization options, especially for permissions and workflows, can feel limited and cumbersome. The mobile app lacks smoothness and features compared to the desktop version, which is frustrating for managing tasks on the go. Additionally, Jira's pricing can get expensive as your team grows, particularly for small companies or teams with tight budgets.
What problems is the product solving and how is that benefiting you?
Jira helps me manage complex projects with task organization, reducing communication gaps through team collaboration. It offers real-time tracking and reporting, supports Agile workflows, and integrates well with tools like Slack. Customizable workflows adapt to any project needs.
Comprehensive Features, But Needs UI Improvement
What do you like best about the product?
I find it easy to organize and maintain projects by splitting them into epics, tasks, and sprints. The story feature is also very helpful. I like the epic feature because it lets me group tasks together. I enjoy the whole environment and find it easy to connect with Confluence for any PRD, SOW, and other documentation work.
What do you dislike about the product?
Sometimes Jira feels confusing and heavy, and I expected a better user experience. The UI/UX is minimalist and lacks attraction.
What problems is the product solving and how is that benefiting you?
Jira makes it easy to organize and maintain projects by splitting into epics, tasks, and sprints. I like using epics to group tasks together. It connects well with Confluence for documentations.
Essential for Issue Tracking, But Agile-Centric
What do you like best about the product?
I use Jira for issue and bug tracking, and I like how it helps to assign responsibilities easily. I also appreciate the sprint reports, which help me understand my team's performance easily.
What do you dislike about the product?
I don't like that you are forced to follow an Agile workflow because it works better with it.
What problems is the product solving and how is that benefiting you?
I use Jira for issue and bug tracking. It helps assign responsibilities easily and understand team performance with sprint reports.
Smooth Process, Great AI Assistance
What do you like best about the product?
I like their problem-solving tasks in Jira, and I find the AI assistant to be perfect for assisting with work. I'm very much satisfied with their driven tools for a smooth process.
What do you dislike about the product?
I usually get functional gaps from their response. They should suggest more, and more tools should be covered for multiple purposes like decision-making and the level of tracking. I think the resources should be more collected for the consumers, even though it's good. Also, features want to be provided more.
What problems is the product solving and how is that benefiting you?
I use Jira for problem-solving tasks. I benefit from their AI assistant, which assists with various work tasks, and I appreciate the smooth process facilitated by its tools.
Effortless Ticketing and Robust Features Make It a Standout
What do you like best about the product?
Jira is the primary tool used by our team to manage software development and project tracking in a professional work environment. I use Jira daily to create and manage tickets, track bugs, plan sprints, and monitor task progress across multiple projects. Features such as customizable workflows, Scrum and Kanban boards, issue linking, comments, and Jira Query Language (JQL) make it easy to track work items and collaborate with developers, QA, and product managers. The reporting dashboards and sprint reports provide clear visibility into team velocity and delivery timelines.
What do you dislike about the product?
Jira has a learning curve, especially for new users who are unfamiliar with agile methodologies or advanced configurations like workflows and JQL. Over time, large projects with many custom fields and integrations can become complex to manage. Additionally, performance may slow down when dealing with very large backlogs or heavily customized instances.
What problems is the product solving and how is that benefiting you?
Jira solves the problem of tracking and coordinating work across cross-functional teams in a structured and transparent way. In my work setting, it centralizes task management, bug tracking, sprint planning, and release tracking into a single platform. This improves accountability, reduces communication gaps, and ensures that all stakeholders have real-time visibility into project status, priorities, and blockers. As a result, our team delivers work more predictably and efficiently.
Concise and Effective Communication Tool
What do you like best about the product?
What I appreciate most about Jira is how it keeps work organized and visible. Tracking tasks, bugs, and overall progress is straightforward thanks to its clear boards and workflows. Jira also supports Agile methodologies, such as sprints and backlogs, which assist teams in planning and delivering their work efficiently. Its customization options and integrations with various development tools enhance collaboration and help minimize confusion. In summary, Jira enables teams to remain aligned, focused, and productive.
What do you dislike about the product?
What I find challenging about Jira is that it often feels complex and overwhelming, particularly for those who are new to the platform. The abundance of fields, settings, and workflows can make processes slower and more cumbersome. At times, it demands additional configuration and ongoing maintenance, and its performance may suffer when handling large projects. Additionally, excessive customization can complicate even straightforward tasks, making them more difficult than they need to be.
What problems is the product solving and how is that benefiting you?
Jira addresses challenges such as tracking tasks, clarifying ownership, and increasing project visibility. It enables me to organize work into stories and tasks, monitor progress, and manage priorities effectively. As a result, my work stays structured, confusion is minimized, team collaboration improves, and tasks are delivered on time with clear accountability.
Streamlined Teamwork with Integrated Jira and Teams
What do you like best about the product?
I like how we can easily create tickets and assign them to the development team with Jira. I also appreciate that it's now integrated with AI, making it easy to rewrite our content. The integration with Teams is great too, as it means we don't have to log into Jira through a browser. We can also integrate Jira with various plugins or use it for test data management, which is pretty handy. Not having to jump between different tools speeds up the development and testing life cycle, which I find really beneficial. If we have access, setting it up is very easy.
What do you dislike about the product?
if build an inbuilt test data management feature will be very useful for automation testing.
What problems is the product solving and how is that benefiting you?
I use Jira for creating user stories and logging defects. It's easy to create tickets and assign them to the development team. Integration with Teams simplifies work by keeping everything in one place, speeding up development and testing cycles.
Robust Issue Tracking, But Setup Can Be Overwhelming
What do you like best about the product?
I like Jira best for its powerful issue tracking and customizable workflows, which make it easy to manage tasks, bugs, and team progress in one place.
What do you dislike about the product?
It can feel complex and heavy, especially for small teams, and setting it up or customizing workflows can be time-consuming.
What problems is the product solving and how is that benefiting you?
Jira solves the problem of tracking work, priorities, and ownership in one place. It benefits me by giving clear visibility into progress, reducing confusion, and helping teams deliver work.
Brings Clarity and Structure to Complex Projects
What do you like best about the product?
What I like best about Jira is that it brings clarity and structure to complexity.
As a Product Owner, Jira gives me a single, reliable place to translate strategy into execution—epics into stories, ideas into deliverables. It makes work visible, traceable, and measurable, which is critical when you’re managing multiple teams, releases, and dependencies.
What stands out most is:
End-to-end traceability from requirements to delivery
Clear ownership and accountability through workflows and statuses
Real-time visibility into progress, risks, and blockers
The flexibility to adapt Jira to different teams without forcing one rigid way of working
In short, Jira works best when things are messy. It helps me stay in control, make informed decisions, and keep delivery aligned with business value—not just activity.
As a Product Owner, Jira gives me a single, reliable place to translate strategy into execution—epics into stories, ideas into deliverables. It makes work visible, traceable, and measurable, which is critical when you’re managing multiple teams, releases, and dependencies.
What stands out most is:
End-to-end traceability from requirements to delivery
Clear ownership and accountability through workflows and statuses
Real-time visibility into progress, risks, and blockers
The flexibility to adapt Jira to different teams without forcing one rigid way of working
In short, Jira works best when things are messy. It helps me stay in control, make informed decisions, and keep delivery aligned with business value—not just activity.
What do you dislike about the product?
What I dislike about Jira, from a Product Owner perspective, is that its flexibility can easily turn into complexity and overhead.
Jira can become heavy if it’s over-customized—too many fields, workflows, and statuses end up slowing teams down instead of helping them move faster. Instead of focusing on value delivery, people start managing the tool.
I also find that Jira sometimes rewards process compliance over real progress. A ticket can look “green” while the actual outcome is still unclear or blocked outside the system.
And reporting, while powerful, often needs constant tuning to stay meaningful—otherwise dashboards become noise rather than insight.
In short, Jira is incredibly strong, but without discipline and product thinking, it can drift from being a delivery enabler to a process burden.
Jira can become heavy if it’s over-customized—too many fields, workflows, and statuses end up slowing teams down instead of helping them move faster. Instead of focusing on value delivery, people start managing the tool.
I also find that Jira sometimes rewards process compliance over real progress. A ticket can look “green” while the actual outcome is still unclear or blocked outside the system.
And reporting, while powerful, often needs constant tuning to stay meaningful—otherwise dashboards become noise rather than insight.
In short, Jira is incredibly strong, but without discipline and product thinking, it can drift from being a delivery enabler to a process burden.
What problems is the product solving and how is that benefiting you?
From a Product Owner perspective, this benefits me in very concrete ways:
It gives end-to-end visibility from idea → epic → story → release, so nothing critical slips through.
It enforces clear ownership and accountability, reducing ambiguity across teams.
It helps me prioritize based on impact and capacity, not just urgency.
It supports predictable delivery through sprint planning, tracking, and release management.
It enables fact-based conversations with stakeholders using real data instead of assumptions.
Overall, Jira allows me to spend less time chasing updates and more time steering the product, managing risk, and ensuring the team is delivering real business value.
It gives end-to-end visibility from idea → epic → story → release, so nothing critical slips through.
It enforces clear ownership and accountability, reducing ambiguity across teams.
It helps me prioritize based on impact and capacity, not just urgency.
It supports predictable delivery through sprint planning, tracking, and release management.
It enables fact-based conversations with stakeholders using real data instead of assumptions.
Overall, Jira allows me to spend less time chasing updates and more time steering the product, managing risk, and ensuring the team is delivering real business value.
Excellent for Real-Time Project Tracking and Cross-Functional Collaboration
What do you like best about the product?
I like the ability of being able to see what is actively being built and what the status of projects is. it is a great tool to collaborate cross-functionally between design, product, and engineering. i also like being able to organize and track everything by project
What do you dislike about the product?
the navigation in jira can get confusing. sometimes i browse tickets and get confused on what i'm looking at because there is alot to look at. i need to familiarize myself with all the terms of space, story, epic, etc
What problems is the product solving and how is that benefiting you?
Jira is solving the problem of coordinating complex work across many people and teams, priorities, and dependencies. This benefits me by creating shared clarity around execution. It turns abstract plans into visible, trackable commitments, making it easier to understand what’s in progress, what’s blocked, and what’s coming next.
showing 91 - 100