Jira Reviews

My main use case for Jira involves managing the complete software development lifecycle in one place. We primarily use it for sprint planning, tracking bugs and development tasks, and assigning work across the developer, QA, and product team.

A typical sprint for our team in Jira usually starts with sprint planning, where the product manager and tech leads create user stories, bugs, and technical tasks in the backlog. Each ticket includes priority, story points, acceptance criteria, and a deadline. For example, during a recent feature release, we were building a new payment integration module. The work was divided into multiple Jira tickets, including an API integration task, a database change task, a UI update task, a testing scenarios task, and a deployment checklist task. We also use Jira Automations during a sprint to automatically notify when code reviews are pending. Bugs created by QA were linked directly to development tasks. A sprint report helps us track velocity and unfinished work.

For small teams, basic task tracking is enough, but once multiple developers, QA, product managers, and stakeholders are involved, Jira helps us create structure and accountability. It centralizes communication, task ownership, timelines, and release tracking in a way that significantly reduces confusion. Another big advantage for us has been historical tracking. Since everything is documented in the ticket, it is easy to go back and understand why a decision was made, when a bug was introduced, or how long a certain work actually took. That is really helpful for planning future sprints and improving estimates.

Jira has had a pretty significant positive impact on our organization, especially in terms of visibility, coordination, and execution speed. Before using Jira heavily, a lot of project tracking happened through chats, spreadsheets, and meetings. As the team grew, it became difficult to track ownership, priorities, and deadlines consistently. Jira helped centralize all of that into one system. One of the biggest improvements was transparency. Everyone—developer, QA, product manager, and leadership—could see the exact status of work in real-time. That reduced confusion and cut down a lot of unnecessary follow-up meetings or manual status updates. Overall, the biggest positive impact has been creating a more organized and scalable way of managing projects, especially when multiple teams are working simultaneously on fast-moving releases.

The best feature, I would say, is that Jira combines project tracking, collaboration, and workflow management into one system. For software teams especially, it becomes the central place where all work happens. Some of the features that stand out to me are Jira's sprint boards and Kanban boards, which make it very easy for tracking work visually. Jira is excellent for tracking bugs and incidents, feature requests, and technical tasks in detail.

For our team, the sprint and Kanban boards in Jira mainly help by giving everyone real-time visibility into the work without needing constant status meetings. During a sprint, the custom boards act as a progress tracker where every task moves through each stage, such as To Do, In Progress, Code Review, QA Testing, or Done. Because the board updates continuously, developers, QA, and managers can instantly understand the current status of a sprint. If too many tickets are stuck in code review or QA, we can immediately identify a bottleneck and can rebalance the work before deadlines are affected. It also helps a lot during daily stand-ups. Instead of everyone manually explaining their tasks, the board easily shows what is actively being worked on, what is blocked, and what got completed recently. Another underrated advantage is workload balancing. A team lead can quickly see if some developer is overloaded while someone else has capacity, and tasks can be redistributed early instead of discovering issues near the deadline. Overall, the board makes project coordination so much smoother because the entire team works from the same real-time view, rather than separate spreadsheets, chats, and status updates.

One additional improvement I would mention for Jira is around balancing flexibility with simplicity. Jira gives organizations a huge amount of customization power, which is great. But over time, many teams end up creating overly complicated processes. After a few years, some Jira environments become difficult to maintain because there are many workflows, custom fields, permissions, and automations layered on top of each other. It would help if Jira would provide a strong built-in recommendation or health check for keeping a project clean or efficient. For example, identifying unused custom fields, suggesting workflow simplicity improvements, flagging redundant automations, or recommending dashboard optimization.

While Jira is very powerful, there are definitely areas it could be improved, especially for usability and simplicity. One common challenge is that Jira can feel overwhelming for new users. The number of features, configurations, workflows, and settings is huge. Onboarding non-technical teams or new employees sometimes takes longer than expected. A simple default experience for a beginner would help a lot. Another issue is performance. In large organizations with heavy customizations, large backlogs, or complex dashboards, Jira can occasionally feel slow, especially when loading filters, reports, or larger boards. Pricing can also become expensive as an organization scales and multiple Atlassian products and plugins are added. Some smaller teams sometimes feel the ecosystem becomes costly over time. The mobile experience would be smoother for project managers or leadership users who mainly want quick update approvals or dashboard views on the go. Overall, Jira's biggest strength is flexibility, but that flexibility can also create complexity if not managed carefully. Improving simplicity, performance, and ease of adoption would make the platform even stronger.

An additional improvement I would mention for Jira is around balancing flexibility with simplicity. Jira gives organizations a huge amount of customization power, which is great. But over time, many teams end up creating overly complicated processes. After a few years, some Jira environments become difficult to maintain because there are many workflows, custom fields, permissions, and automations layered on top of each other. It would help if Jira would provide a strong built-in recommendation or health check for keeping a project clean or efficient. For example, identifying unused custom fields, suggesting workflow simplicity improvements, flagging redundant automations, or recommending dashboard optimization.

I have been using Jira for the last four years.

Jira is pretty much stable from my experience. We have never encountered any types of issues with Jira. Downtime is very rare.

In terms of scalability, Jira is generally very strong, which is one of the main reasons large organizations adopt it. In our experience, Jira scales well across team size growth, multiple departments, larger project portfolios, and complex Agile environments. Overall, Jira scales very well for enterprise use cases, especially when organizations invest in good administration practices and keep workflows reasonably streamlined. That combination of flexibility plus enterprise scalability is one of Jira's biggest strengths.

Customer support has been pretty good in my experience. The customer support of Jira has been generally good, especially for standard product use cases and documentation support. Support quality depends a lot on the subscription tiers and complexity of the use cases. Overall, I would describe the support experience as solid but not perfect. Atlassian's biggest strength is its self-service ecosystem: documentation, community discussions, and integrations, while the biggest improvement area is faster, personalized support for complex cases or urgent escalations.

Before fully standardizing on Jira, teams used a mix of simple project tracking methods and lighter tools, depending on the department. Some work was managed through spreadsheets, email threads, shared documents, and basic task management platforms. While other approaches worked for smaller teams, they became difficult to manage as projects grew complex. The main reason we switched to Jira was for better scalability, strong Agile and sprint management support, improved bug tracking, and centralized visibility across the project.

In terms of pricing and setup cost, my experience with the pricing and licensing of Jira was generally positive, especially compared to the operational value it provides for project management and collaboration. The cloud subscription model made the initial setup relatively straightforward because we did not need to invest heavily in infrastructure, servers, or a dedicated maintenance team. That reduced the upfront cost and setup cost significantly compared to traditional, on-premises tools. From a licensing perspective, the user-based pricing model is easy to understand and scale. Atlassian offers different tiers, such as Free, Standard, Premium, and Enterprise, depending on the team size and feature requirements. For a small team, the pricing feels reasonable because even the lower-tier plans provide strong functionality for sprint management. Overall, Jira offers good value for an organization that actively uses its capabilities, but companies should plan carefully for long-term scaling costs, especially in large enterprise environments with many users and plugins.

My biggest advice for a team considering Jira is to keep the implementation simple in the beginning. A lot of organizations try to customize everything immediately: complex workflows, dozens of statuses, too many custom fields, and excessive automation. That often makes Jira harder to use instead of more effective. It is usually better to start with a clean and practical workflow, standardize the process gradually, and only add complexity where there is a real business need. Another important recommendation is to define ownership and governance early. Jira scales very well, but without good administrator practices, an environment can become cluttered over time. Having real standards for the workflow, naming conventions, permissions, and customizations helps maintain long-term usability. Finally, focus on Jira to improve collaboration and visibility, not just process control. The teams that get the most value from Jira are usually the ones that use it to create transparency and alignment, rather than turning it into an overly rigid management system.

We have definitely seen a positive return on investment after adopting Jira more broadly across the team. The biggest ROI came from improved operational efficiency and reduced coordination overhead rather than direct headcount reduction. One clear improvement was time saving in project tracking and communication. Since Jira centralized sprint planning, task ownership, bug tracking, and reporting, the team spent much less time managing work manually through spreadsheets, long email chains, or repeated status meetings. We saw fewer follow-up meetings, faster identification of blockers, and quicker issue resolution times. For engineering managers and tech leads, dashboards and automated reporting save significant administrative time every sprint because progress tracking becomes largely self-service. Another ROI area was delivery predictability. Better sprint visibility and backlog management reduced last-minute surprises. Overall, the ROI mainly came from improved team productivity, better project visibility, reduced coordination efforts, faster issue tracking, and more predictable delivery execution.

In terms of pricing and setup cost, my experience with the pricing and licensing of Jira was generally positive, especially compared to the operational value it provides for project management and collaboration. The cloud subscription model made the initial setup relatively straightforward because we did not need to invest heavily in infrastructure, servers, or a dedicated maintenance team. That reduced the upfront cost and setup cost significantly compared to traditional, on-premises tools. From a licensing perspective, the user-based pricing model is easy to understand and scale. Atlassian offers different tiers, such as Free, Standard, Premium, and Enterprise, depending on the team size and feature requirements. For a small team, the pricing feels reasonable because even the lower-tier plans provide strong functionality for sprint management. Overall, Jira offers good value for an organization that actively uses its capabilities, but companies should plan carefully for long-term scaling costs, especially in large enterprise environments with many users and plugins.

Before we were fully adopting Jira, other project management and issue tracking tools were evaluated. We evaluated other options such as Trello, monday.com, Azure DevOps, and ClickUp. Each tool had its strengths depending on the use cases. For example, Trello was very easy to use and visually simple but felt limited for large-scale Agile development and advanced workflows. Azure DevOps was a serious contender because of its strong integrations with the Microsoft ecosystem and development pipeline, but Jira offered more flexibility and wider adoption across a mix of teams. The final decision largely came down to Agile project management capabilities and workflow customizations, integration ecosystem, and scalability. Jira simply aligned better with the complexity of our development process and cross-team collaboration needs.

An additional thought about Jira would be that its real value becomes more apparent over time as teams and projects grow in complexity. At first, people see Jira simply as a ticketing or task tracking tool, but once it is integrated properly into the development, QA, release management, and planning process, it becomes a central operational platform for organizations. I also think Jira works best when teams treat it as an enabler for collaboration and visibility rather than just a management or reporting system. Organizations that keep workflows practical and focus on transparency usually get the strongest results from it. Overall, despite some complexity and learning curve challenges, Jira remains one of the most mature and capable platforms for Agile project management and software delivery at scale. I gave this review a rating of nine out of ten.

My main use case for Jira is agile project management and issue tracking. We use it to manage sprint planning, track development tasks, monitor bugs, prioritize feature requests, and coordinate work across the development team. It serves as a central platform for organizing work and tracking project progress from planning through release.

In a recent web application project, we used Jira to manage the development of our user authentication model. We created user stories for features such as login, registration, and password reset, then broke them into smaller development tasks. Each task was assigned to team members in a sprint, and we tracked progress through a Kanban board. For example, I personally worked on a bug ticket related to session timeout handling, which was logged in Jira, prioritized during sprint planning, and then moved through in-progress, code review, and done stages as I completed and verified the fix.

One thing unique about how we use Jira is that we heavily customize workflows to match our development process. For example, we added extra statuses such as Ready for QA and Blocked to make it easier to track wherever each task is stuck in the pipeline. We also make strong use of dashboards and filters so each team member can quickly see their sprint workload, high-priority bugs, and overall project progress.

Jira's scrum and Kanban boards are the best features because they give real-time visibility into sprint progress and task ownership. We also rely heavily on customizable workflows, which allow us to match Jira to our exact development process, such as adding in-review or blocked statuses. Another strong feature is reporting and dashboards. Burn-down charts, velocity tracking, and sprint reports help us measure team performance. Finally, integrations with tools such as GitHub and CI/CD pipelines are very useful since they connect code changes directly to Jira tickets and keep everything traceable in one place.

Jira's scrum and Kanban boards are the most critical feature of our daily work because they give us real-time visibility into exactly what everyone is working on, what's in progress, and what's blocked. It essentially acts as a single source of truth for our development workflow, which keeps the entire team aligned and helps us deliver more work efficiently.

Jira's automation and reporting features are more powerful than many people realize when used properly. For example, you can automate repetitive actions such as moving tickets between statuses, assigning reviewers, or triggering notifications when code is merged. This saves considerable manual work that teams often do not realize they can eliminate. Additionally, the reporting and filtering system is more flexible than many people expect. You can create highly specific dashboards to track sprint health, team workload, and bottlenecks in real time, which helps with decision-making beyond basic task tracking.

Jira has had a very strong positive impact on our organization by improving visibility, coordination, and delivery speed across the team. The team spends less time on manual coordination and status updates. Sprint planning has become more realistic, which has reduced last-minute rushes and helped us deliver features more consistently on schedule. In communication, it has reduced dependency on meetings and ad-hoc messaging. Most updates are handled directly through tickets, comments, and workflow status changes, which keeps communication more structured and traceable.

Jira is very powerful, but there are a few areas where it could be improved. The user interface could be simpler and more intuitive, especially for new users. Performance could be better on large projects. Workflow configuration could be easier. While it is very flexible, setting up or modifying workflows often requires too many steps. Additionally, better built-in onboarding and documentation inside the product would help new users understand features such as automation and reporting without needing external resources.

Jira could improve consistency in navigation and search across larger projects. Our team also occasionally struggles with the permission complexity. Managing access levels across multiple projects and teams can become time-consuming, especially when onboarding new members or restructuring the teams. The automation rules setup is powerful, but not always very beginner-friendly.

I have been working with Jira for around two years.

Jira has been very stable overall. We rarely face downtime or critical system outages.

Jira scalability is one of the strongest aspects in our experience. From a team perspective, it scales very well. In project complexity, it scales very well. We have noticed that as projects become very large, things such as search performance, build complexity, and dashboard loading times become slightly slower. Overall, Jira is highly scalable for both team size and project complexity.

Jira's customer service is very good.

I recommend defining your team's workflow before fully implementing Jira. Jira is very powerful, but it works best when you take time to properly set up your project structure, workflows, and permissions from the beginning. I would also recommend starting simple and using basic scrum or Kanban boards first. Finally, invest a bit of time in training the team.

We do not have any business relationship with Jira or its vendor.

We have seen a clear ROI, mostly in terms of time savings and improved delivery efficiency rather than direct cost reductions. We estimate that the team spends roughly 20 to 30 percent less time on status updates, sprint tracking, and task clarification since everything is central to Jira. In terms of delivery efficiency, sprint planning is more accurate, which has reduced rollover work and improved on-time delivery of features. From a cost perspective, we have not reduced headcount, but we have improved output per developer. ROI is best described as higher productivity, better predictability, and reduced coordination overhead rather than direct financial savings.

Jira operates on a subscription model, typically priced per user. It is quite affordable, and the setup cost is low. Licensing is simple and easy to get started with.

Jira's AI security capabilities are improving, but they still feel somewhat early stage compared to dedicated AI security platforms. Most of the AI features today are focused on productivity, such as summarizing tickets, suggesting content, and helping with issue creation, rather than advanced security intelligence. Overall, security is solid at the platform level, but AI-assisted security is still an area with room for growth.

Jira's AI capabilities are useful but not always perfectly consistent in accuracy or depth. When the data is incomplete or unclear or highly technical, the AI-generated suggestions can sometimes be too generic and miss important project-specific details. It still relies heavily on the quality of the ticket content and project setup. In terms of reliability, it is stable for everyday use cases, but I would not fully depend on it for critical decision-making. It works best as an assistive tool rather than an authoritative source. Overall, Jira's AI features are helpful for productivity and summarization but still need human validation for accuracy in more complex scenarios.

I would rate this review at nine out of ten.

Jira is used for project management, which is the main use case and is primarily handled through Jira.

The typical workflow for project management involves using Jira to follow Agile practices with sprints. Each sprint, tasks are allocated to people and completed within the sprint itself. Sprint planning, sprint execution, and sprint retrospectives are all handled by Jira.

Jira is mainly used for sprint activities and sprint retrospectives, and Jira APIs have also been used for data science projects.

Jira positively impacts the organization as it helps Scrum masters easily manage projects in a way that integrates with Agile practices such as creating sprints.

Since using Jira, specific outcomes have been observed such as organizing projects into meaningful features and chunks, which eventually helps deliver features and the project faster, making it very time-saving.

Jira has a very good interface and it is very easy to manage sprints, tasks, and epics. The main feature is the hierarchy, as features can be converted into epics and topics, allowing bigger tasks to be partitioned into smaller ones.

The hierarchy feature in Jira helps the team significantly compared to other tools that have been used, such as Trello, which is mainly useful only for a waterfall model. For modern Agile practices, Jira is the most adapted tool in the industry.

Another valuable feature is that Jira APIs have been used for data science projects to analyze tasks and get insights. This has also been very helpful in the project.

One feature that could improve Jira is the integration of AI capabilities, such as organizing Jira tasks autonomously with minimum human intervention and executing aggregations and clustering of these tasks. This would help Scrum masters reduce their task management time tracking and other related activities.

In terms of needed improvements, it would be appreciated to have more reporting capabilities in Jira, such as easily exporting capabilities to show how tasks are in progress and how the team is performing well or poorly. It would be great to have all these kinds of feedback in a single file.

I have been working in this field for the past eight years.

Jira has been used since the beginning of my career, for almost eight years.

In my experience, Jira is stable, with around 99% uptime, and issues have only been faced in terms of latency on very few occasions.

Whenever there are issues, the internal Jira enterprise team is contacted directly, and if it is something beyond that, it is escalated to Jira customer care, but typically the internal team is contacted only.

Previously, Trello boards were used in the earlier times when waterfall methodologies and Kanban methodologies were followed. However, after the industry switched to Agile practices, Jira has been used.

A return on investment has been seen with Jira, as a lot of time has been saved in arranging tasks, converting software features into epics, tasks, and milestones, making it easy to track progress and plan future roadmaps.

Before choosing Jira, Monday.com was evaluated, but it was found that Jira is a more capable software compared to others in the market.

My advice to others looking into using Jira is that it is a very good tool and the best tool in the industry for current Agile methodologies and Scrum methodologies. Overall, Jira is a very good tool and one of the best tools in the industry for Agile practice. The review rating given is 9.

In the current company, we use Jira for pretty much everything, including project management, task tracking, release planning, and communication. It's our day-to-day ecosystem for the whole team.

We use Jira for technically everything in my daily work. We use it to task developers, and we use it for marketing tasks. It's the system which allows us to track everything and use it as a central hub where everyone works.

Jira is stable.

The biggest advantage Jira offers is flexibility because it's very flexible. I never use default templates and prefer to customize everything to fit how the project management and task management system meet the business needs. The biggest advantage is you can build your own workflows and make it work exactly the way your team needs and integrate it with almost every third-party software.

Jira helps us to be more organized, to track every particular task, and manage permissions about who has access to what. I'm entirely happy with how Jira is flexible and I see a growing number of add-ons that can be customized deeply, though sometimes they look even too complex.

I don't have a particular customization or integration that's been especially valuable for my team, but I experienced integrating Jira and QuickBooks, which was very challenging, but it really impacted the efficiency of the whole company.

I have been working with Jira for over 12 years, and I've seen it grow every year. It's a powerful product, but lately, I think Atlassian has been adding too many simplified features that look nice but don't offer the same level of flexibility, and made some fields not available through the API, which is kind of frustrating. If I could make one suggestion, it would be to focus more on improving API integration and automation tools, not just the design.

I have been using Jira for 12 years.

Jira is stable.

Scalability for Jira is great, and it handles growth easily from 100 to thousands.

Jira's customer support is one of the best I have ever dealt with because they respond quickly, and if it's something complex, they even jump on a call, which is not usual.

Positive

I've used Trello and Monday, and even a few in-house systems, and usually, for project management, people are using project management tools like Microsoft Project and Project Server, but for task management, Jira is the best one, also for project management because it provides even Gantt diagrams.

It's always hard to measure ROI precisely, but overall, the development time usually pays off within a year through efficiency gains and saving efforts.

Jira itself is fairly priced for the features it provides, but pricing is a bit higher than some alternatives, mostly because many plugins and add-ons are paid and licensed per user. So even if only five people in your team use a financial plugin, you still pay for all 100 seats.

I would rate the customer support a 10 on a scale of 1 to 10.

You may work with Jira only if you have enough internal resources to automate it and to build your own processes and flows because it's very flexible, but default templates might not be as effective as you expect since they're pretty much average. But if you have an internal development team and resources for supporting Jira, I think it's the best solution.

On a scale of 1-10, I rate Jira a 9.

I use Jira mainly for report tracking and bug tracking, as well as tracking and managing work items such as tasks, bugs, and user stories, sprint planning, and backlog management for Agile teams, monitoring progress through boards, workflows, and status updates, and coordinating across teams with clear ownership and priorities, and generating reports and dashboards to track delivery, velocities, and bottlenecks.

In a recent sprint, my team used Jira to manage a feature enhancement. The product owner created user stories in the backlog with clear acceptance criteria. During sprint planning, we broke these stories into tasks and assigned them to developers and QA. As work progressed, the team moved issues across the board: to-do list, in progress, code review, testing, and done. This provided everyone real-time visibility into the status. We also logged bugs during testing and linked them to the original stories, making it easy to track fixes before the sprint closed.

I use Jira to add bug stories that arrive during testing and check the life cycle of the bug, and close and assign them to different developers.

The best features that Jira offers are planning and tracking. It provides customizable workflows and Agile boards using Scrum and Kanban and backlog management. For reporting, it provides sprint reports and burndown charts. The dashboard widgets are used to build live dashboards with charts and filters tailored for my needs. Jira also provides collaboration features through issue linking and dependencies, comments, and mentions for different users.

Out of these, I rely most on planning and tracking in my day-to-day work because it is where all work starts and stays organized, from backlog grooming to sprint planning. Agile boards give instant visibility into what is in progress, blocked, or completed. It provides clear status and ownership, which helps the team stay aligned without constant follow-ups. Daily stand-ups and sprint reviews are much more efficient since everyone is looking at the same source of truth. Dashboard and reporting are close seconds, especially for sprint health and leadership updates, but planning and tracking is what I interact with the most on a daily basis.

Another point worth highlighting about Jira features is how flexible and scalable they are. Custom fields and issue types let teams capture exactly the information they need without overcomplicating things. Permission and role-based access makes it easy to collaborate across teams while maintaining control and governance. Search and filter options are extremely powerful for quickly finding issues, creating saved views, and driving reports and dashboards.

Jira has had a strong positive impact on my organization. It improved visibility and transparency. Everyone from team members to leadership has a clear, real-time view of work status, priorities, and blockers. Better planning and predictability resulted from structured backlog, sprint planning, and historical data, which have improved delivery forecasts and sprint commitment. Team alignment increased through standardized workflows and shared goals that keep cross-functional teams aligned and reduce miscommunication. Faster issue resolution is provided by Jira by centralizing tracking and linking issues, which helps identify dependencies and address bugs and blockers more quickly. Jira reduces manual efforts through automation and integration, minimizing repetitive tasks and streamlining handoffs between teams.

I have definitely seen measurable results from constantly using Jira. Sprint predictability improved with sprint commitment versus completion rates increasing and fewer carryover stories between sprints. Faster time cycle resulted from reduced average time for in-progress to done due to better visibility of blockers and clear workflows. Defects leakage reduced because bugs are logged, linked, and tracked earlier, resulting in fewer issues escaping to production. Less time is spent on status updates through dashboards and boards that reduce manual reporting and follow-ups, saving several hours per sprint. Team accountability improved through clear ownership and audit trails that lead to quicker responses and fewer stalled tasks.

Jira is a powerful tool, but there are definitely areas where it could be improved to make day-to-day use even better. A simpler user experience for new users is necessary. The interface and configuration options can feel overwhelming, especially for non-technical and first-time users. A more guided onboarding would help. Performance at scale is another consideration. On large projects with many issues, filter boards and reports can sometimes feel slow. Faster load times would improve productivity. Fine-grained control over notifications should also be available to help users avoid alert fatigue.

I have been working in my current field for the last five years.

Here is the advice I would give to everyone considering Jira. Start simply by not over-customizing the workflow or fields on day one. Begin with Jira standard templates and evolve as your process matures. Use Jira as a single source of truth. Apply automation thoughtfully, as automations can save time, but too many can make the workflow hard to understand. Use sprint metrics and retrospectives to continuously improve how Jira is configured and used. Overall, Jira works best when it supports your process rather than trying to force a process around the tool. I would rate Jira an eight out of ten.

I am using Jira for project management. To track work items in Jira, work items are mapped to the subtasks that we have in our workflow. Our workflow is designed so that once the program is specified, epics are defined. Epics are mapped with a couple of stories and subtasks.

We create items in Jira and have specific mandatory fields like end date and time duration that we must fill out. There is a checklist, and if it is a technical task that has a dependency with other teams, we have a checklist for the review. Someone will fill the data for that checklist, either a review lead or a peer. The same person does not fill the data. The closure of the task cannot be done by the person who creates it; it must be closed by someone else, either a review leader, peer, or someone with a dependency delivery.

Jira stands out for task tracking; if it is properly configured based on the program, it can be tracked and projected for the workbench structure. Jira burndown charts and burnup charts can be used properly. I can see how many Jiras have been closed and how many are open, which can be tracked very easily. Milestones can be used for tracking milestones, and that is the best part of it that people are using.

When tracking Jiras where the change is deployed, Jira will be tentative for closure. We have different tools to update the results and validation results into Jira, and those details can be used as a dashboard of Jira content to show management how many are on hand, closed, or running.

Regarding the features in Jira, sprint types and sprints, if properly configured and designed, can have the current sprint review mapped in Jira. The next sprint review can be mapped for the feature working in Jira, and post-outdated items can also be added as impediments, for which I can raise a ticket. If it is configured with GitLab or Git, it can populate what kind of Git hooks are configured, which can then be populated in Jira so that manual updates to Jira are not necessary.

In day-to-day use, today's Jiras serve as a way of tracking for tomorrow's list, helping to track down items. If I am using automation, it can hook up to any other task, whether in automation test cases, automation test frameworks, CI/CD frameworks, or CRM frameworks; anything can be tailored based on the need.

Jira has positively impacted my organization in terms of productivity measures, tracking individual productivity, group productivity, domain productivity, overall productivity, and helping other dependent teams. It is also a part of monitoring.

Jira stands out for task tracking; if it is properly configured based on the program, it can be tracked and projected for the workbench structure. Jira burndown charts and burnup charts can be used properly. I can see how many Jiras have been closed and how many are open, which can be tracked very easily. Milestones can be used for tracking milestones, and that is the best part of it that people are using.

In day-to-day use, today's Jiras serve as a way of tracking for tomorrow's list, helping to track down items. If I am using automation, it can hook up to any other task, whether in automation test cases, automation test frameworks, CI/CD frameworks, or CRM frameworks; anything can be tailored based on the need.

Jira has positively impacted my organization in terms of productivity measures, tracking individual productivity, group productivity, domain productivity, overall productivity, and helping other dependent teams. It is also a part of monitoring.

One area where Jira could be better is regarding the APIs from the sponsoring team; they should provide clearer API endpoints and support, as well as more flexibility in the support level.

When I say the API support should be clearer, I mean the APIs that they are providing; if something is not working or if people are enabling it, or if there are new tools or features adapted in Jira, that information should be distributed.

I do not have any bugs to report; it is a UI tool, but it should have better integration with other tools, and components outside the market, especially open-source options, should be more popularized. Currently, I do not see any open-source options being pluggable or plug-and-play configurations.

I would rate Jira an 8.5 based on the current support with different tools, domains, and components. The reason I chose this number, reduced from a 10, is that while it is close to a 10, there are still gaps in endpoint support and other supports.

In terms of stability, unless I feed the data correctly, reliability is ensured with Jira.

As the number of users, projects, and work items grows, Jira can scale effectively. It is very scalable, and many organizations use it.

Customer support for Jira has been provided through a separate team, and support is available based on the licensing, whether it is on a yearly basis or a two-year basis.

I would rate the customer support an eight.

Before Jira, people were using different tools that were not fixed. In my organization, Jira is very powerful and can scale in a significant way. Prior to that, based on the programs, some of our programs were customized with different IBM tools or open-source tools.

An evaluation was done regarding usage based on the program, and after that evaluation, we opted for Jira.

Jira is deployed in my organization as a private cloud setup, specific to the organization; it was previously on-premises.

Definitely, there has been a return on investment from using Jira. While I would not say there has been reduced effort, tracking has helped people see productivity measures and different observability metrics and traceability metrics of different tools. Everything from the requirement to validation is embedded in Jira, so traceability is also met to some extent.

I do not think there is anything else we did not cover; I believe I have answered most of the questions and queries in general. My overall rating for this product is 8.5 out of 10.

My main use case for Jira is managing agile development workflows, tracking tasks, bugs, and sprint planning, and coordinating with cross-functional teams by sharing updates on Jira so that every team can be updated at the same time without connecting every time and wasting a lot of time.

In a recent back-end project, we used Jira to manage sprint-based development, and I created epics for the major modules, broke them into user stories and subtasks, tasked the bugs through the workflows, and used sprint boards to monitor progress and blockers during the daily standups.

Jira has improved transparency and collaboration across the team, helped us track work more efficiently, reduced missed tasks, and managed releases better, making the overall sprint planning and delivery smoother compared to earlier struggles.

After adopting Jira more effectively, our team improved sprint completion consistency, significantly reduced missed tasks through better tracking, and shortened the release cycle by improving visibility into blockers and dependencies.

One thing I really appreciate about Jira is how customizable the workflows and dashboards are, as it makes it easy to track priorities, team progress, and release timelines in one place.

From my perspective, the best features of Jira are customizable workflows, sprint and backlog management, the powerful dashboards and reporting features, along with integrations with tools such as Git and Confluence, and its strong issue tracking capabilities.

I rely the most on the sprint boards and workflows tracking in Jira because they give clear visibility into task status, priorities, blockers, and overall team progress in real time.

Another useful feature in Jira is its automation support, which helps reduce manual work by automatically updating the status, assigning tasks, and sending notifications based on the workflow rules.

Jira could be improved by making the UI simpler and more intuitive, especially for new users, as performance can also slow down in large projects, and configuring workflows or dashboards sometimes feels complex.

I would also appreciate seeing better reporting customizations, a lighter interface for faster navigation, and easier onboarding for non-technical users using Jira for the first time.

I have been working in my current field for the last three years.

Jira is stable and reliable for day-to-day project management, as we rarely face major downtime issues, and it handles team collaborations and large workloads consistently very well.

In terms of scalability, Jira is highly scalable and works well for both small teams and large cross-functional projects, supporting a growing user base, multiple workflows, integrations, and enterprise-level project management needs.

The support offered by Jira has generally been good in my experience, with strong documentation and community support, resolving most issues reasonably quickly, although response times for complex problems can take longer.

Before Jira, we mainly used spreadsheets and simpler task management tools that lacked a structured flow, detailed tracking, and agile project management features, which is why we switched to Jira.

The pricing of Jira feels reasonable for the features it provides, especially for agile team management and integrations, with setup being fairly straightforward with the cloud version, but the licensing cost can increase noticeably as team size and advanced feature usage grow.

We have seen a positive return from using Jira through better task visibility and improved sprint completion rates, alongside reduced manual tracking efforts that save a lot of time and enable faster issue resolution across the teams, which previously used to require meetings for bug assignments.

Before choosing Jira, we evaluated tools such as Trello and Azure DevOps, but the features offered by Jira were superior, so we proceeded with it.

My advice would be to properly define workflows and project structures before implementing Jira, starting with a simple approach to avoid over-customizations early on, and ensuring that the team is trained well to get the most value from the platform.

Jira is a strong and reliable project management tool, especially for agile teams, offering great flexibility and tracking capabilities, and keeping workflows simple helps teams to get a better experience from it, definitely improving overall productivity. I would rate this product an eight out of ten.

My main use case for Jira is project management based on my personal experience, as I use it for task management and time tracking, along with integration with other applications. The automation part with Jira is excellent. For example, when I use smart commit, I can see all the specific Jira ticket details in Bitbucket as well. When I create any branch using a Jira ticket, I get that branch link into the particular Jira story.

Most companies are following Agile methodology, and I follow the same approach. Whenever a new feature comes to our organization, we first create stories and connect with the team to assign story points. Each story has story points that help us decide the complexity of the story and how much time it will take. I personally prefer story pointing over t-shirt sizing.

Everything that Jira offers is outstanding. Time tracking, task management, and the platform Jira provides allows us to play games like Planning Poker. We can plan our sprint using Planning Poker, and we can analyze our velocity and burndown chart.

Time tracking means that as a team, we work on different stories, and since we work remotely from home, each person can easily track how much time they have spent with the help of a Jira ticket. Planning Poker helps us with story pointing for a particular story. We are able to execute our sprint in a very structured manner when we perform Agile properly. The tracking of each resource is quite easy, and we can get everyone's time slot and see how much time they have spent in a particular month.

This has increased team productivity, and we can also analyze which resource has bandwidth. We usually work from 10 to 7, so if a person has spent 10 hours, we can appreciate them for doing extra work to complete a particular task. We can also analyze a person who is spending only four hours in a week, and we can give another task to them. This obviously increases our productivity and makes project delivery much easier.

I rated Jira 10 out of 10 because it gives the flexibility to track the complete project. We have sprint planning, active sprint, and different types of graphs with which I can analyze my project health. Anyone from the management team can come to me, and I can easily show them the progress of the project. Tracking the project, tracking time, and tracking the health of the project is quite easy.

From my experience using Jira, I would say Jira is doing great and needs no improvements at this time.

I have been using Jira for seven years.

Jira is totally stable.

The scalability in terms of organization is increasing day by day. We have a scalable Jira performance in our organization.

Jira has a very decent product, and from the last seven years, we have not encountered any issue that required us to reach out to a customer support team.

If you want to track your project into Agile methodology, I would suggest you should go with Jira. Jira has everything in a single platform. Jira also has automated tools, and now Jira supports AI as well. Jira is good for a product that wants to grow in the market in a decent timeframe.

I would say the return on investment is about time saved, and if we are able to save time, it directly saves money as well. I can explain how we are saving time and money. We are creating stories in chunks, and each story has some sub-tasks. If we get stuck on one task, we easily switch to another task. After getting the complete detail on a particular sub-task, we implement it and track it with the help of the time tracking feature, which makes it quite easy to manage everything in a single platform.

As far as I use Jira, I would rate it as 10 out of 10.

As a customer support representative or a customer engineer, my main use case for Jira involves issuing Jiras to other teams where customers present or reach out to us with certain issues related to our product. When I was working at another company as a quality engineer, I also had experience managing templates and adjusting them as I was primarily working on issuing bugs in the scope of product testing.

I created a recent Jira ticket after speaking with one of our engineers as we were receiving a lot of similar reports of the app crashing, and after looking everything up in Sentry, we understood that there is indeed an issue with the app. We have a board in Jira for customer requests where I created the issue, and it was duplicated in our web team's board as an official bug. That was the most recent case where I have used Jira.

The best features that Jira offers include the ease of tracking everything. I love Jira dashboards where you can track the data that you are interested in. I love the agility of the board management and the possibility of adjusting all the templates per board. Overall, I think it is a very useful tool for teams to be on track and to be on the same page. For example, if I am out of the office for a couple of days and then I return, I have easy access to understanding what has changed since I left and what the news are.

In my past experiences, I was the one creating dashboards for the issues that our team created, which helps us with our day-to-day operations. The reason that it is very important to us is because it gives a one-stop-shop to all the team members to be on the same page and decreases the chance of creating any duplicate tickets. It makes sure that everybody is on the same page, and we use it on a weekly basis to sync and inform our teammates about the new issues that we have raised.

Jira has helped not only our organization but many organizations to be very focused and understand what needs to be done and to prioritize things effectively. The board that I am speaking about, as far as customer issues are concerned, is a fairly new concept in our company because prior to that our escalation flow was just a written escalation in Slack and the communication there. Now it is more focused and aligned with the team because we do not take resources from the engineering and QA team. We just issue the report once we make sure that it is actually a bug, and it gets handled. This has helped save time and make everything more manageable and more focused.

I would recommend Jira for scalability as well, considering its ability to be extremely customizable and to meet any team's needs. I have used Jira in a team of ten people and in a team of five thousand people, so I consider this a very scalable tool.

It is really hard to say right now how we can improve Jira because it is already in a very good place. I think it comes down to the customization that is applied to each team, which Jira allows all the teams to do based on their pricing plan. There is not much that I think could improve, other than maybe a better integration with Notion because with Confluence, you have great integrations in Jira and are able to pull out data directly from Jira, while in Notion, it is a bit limited. A better integration with Notion would be very helpful.

I have been using Jira for about five years since I started working in IT.

I have not experienced stability issues with Jira.

I have not experienced scalability issues with Jira.

I have had the chance of reaching out to their customer support a couple of times, and my experience has overall been very positive because they usually reach out within one to two business days and give specific answers.

I have not been involved with the setup process in this company. However, as part of my previous roles where I was making some adjustments to our existing boards, I started trials with Jira to try to replicate something in my trial board and then to copy it in our existing boards. Everything was very straightforward. I created free accounts and was able to do everything that I would be able to do in my organization's Jira. Other than that, I do not have much experience with this.

Using templates in specific Jira boards helps us save time by ensuring that all the tickets have the same structure and include the same relevant information that will help relevant teams. For example, in my previous experience for bugs, we had specific templates that had to be followed up. Different people from different departments were creating issues which were easily understandable by QAs. Having worked as a QA myself and using Jira, I can assure that it saves a lot of time by having these templates and knowing what needs to be filled in and what does not need to be filled in, while communicating this with our project manager to make adjustments to our template. If I receive any bug report from our customers, I try to reproduce it first before I issue a Jira ticket or before I even reach out to our QAs, which basically gives them more time and takes less time from them to confirm whether it is expected behavior or a bug. I create the bug, and using automations, I create a bug in our customer-specific board, which gets duplicated in our web or app board where it gets verified by the QAs.

My advice for others looking into using Jira is to make sure that you customize it to your needs, as it is extremely customizable. Using it out of the box might seem very hectic and not particularly useful for your use case, but making sure that you customize it based on the boards, templates, and other elements, and have all your relevant data in your Jira dashboards is extremely useful. Try to find ways to incorporate Jira into tools that you already use, such as Slack, Confluence, or something else, as it will be very helpful to stay consistent across the board.

I overall recommend Jira to any teams that are working on software products as it makes everything easier. This can be used by marketing teams and sales teams who are trying to reach out to different customers or who have a big project to manage, so it is a great project management tool. I would rate this product nine out of ten.

I have ten minutes to answer questions regarding Jira, and the questions include which features I prefer, how I use the tool, and what needs to be improved. Jira has impacted the productivity and cost efficiency for me and my development team, though I have faced some challenges with Jira during this time.

The features of Jira that I find most useful for my work is the capability to manage. Jira has impacted the productivity and cost efficiency for me and my development team, though I have faced some challenges with Jira during this time.

I have some knowledge about improvement. What I think should be improved in Jira to make it better for the next release could be in terms of some additional features, support, cost, or deployment.

To improve Jira, maybe some AI features could be added.

I have been using Jira for a few years, approximately two to three years.

For configuration and deployment, it takes a certain time, and regarding scalability, it is scalable for my environment and easy to scale.

I did not face any issues with stability or upgrades. Regarding technical support, I have never consulted the support of Atlassian for any issues.

For configuration and deployment, it takes a certain time, and regarding scalability, it is scalable for my environment and easy to scale.

I did not face any issues with stability or upgrades. Regarding technical support, I have never consulted the support of Atlassian for any issues.

Positive

I have hands-on experience with other tools that I am personally using, such as from Microsoft or service management and CRM.

I have hands-on experience with other solutions but not at the level of an expert. I'm managing a department with people that do this on the job.

Jira is easy to set up.

I can send an email first to get the contact number of the person from my team who is an expert in Defender.

Jira has impacted the productivity and cost efficiency for me and my development team, though I have faced some challenges with Jira during this time.

I can definitely recommend Jira to those people who are planning to use it. On a scale of 1-10, I rate Jira an 8.