Jira Reviews & Product Details

What I like most about Jira is how it keeps my daily work organised and makes team coordination easier. I have been using it for around 3 years as a Senior DevOps Engineer, and it has become an important part of my workflow.

I regularly use Scrum and Kanban boards to manage sprint tasks, track progress, and monitor pending work. Creating tickets, assigning tasks, and updating statuses is straightforward. The filters and dashboards are especially helpful. For example, during deployments, I can quickly find high-priority bugs and pending issues without checking every ticket individually.

I also like its integration with tools like Confluence and Bitbucket, as it keeps technical discussions, documentation, and code updates connected. Jira has been reliable even when handling multiple projects and a large number of tickets, although detailed reports can sometimes take longer to load.

The pricing feels reasonable considering the features it offers. Getting started was fairly easy, and its documentation and online community have been helpful whenever I needed support.

I also find automation useful for assigning issues, sending notifications, and updating ticket statuses, as it reduces repetitive work. Its AI features can also help summarise issues and find information faster.

Overall, Jira gives me a clear picture of team progress, pending tasks, and urgent issues. After three years of use, I appreciate how much easier it makes managing projects and coordinating with different team members. Review collected by and hosted on G2.com.

One thing I feel Jira could improve is its overall ease of use. Since I have been using it for around 3 years as a Senior DevOps Engineer, I find that some features take more clicks than necessary, especially when switching between projects, boards, and issue details. The interface can also feel a little crowded when handling multiple tasks at once. Making navigation simpler would save time during daily work.

Another area is integrations. Jira works well with tools like Bitbucket, Confluence, and other DevOps tools, but sometimes setting up integrations or managing permissions requires extra effort. A simpler setup process and clearer error messages would make things easier.

In terms of performance, Jira generally works reliably, but larger projects with many issues, filters, and dashboards can sometimes take longer to load. Improving loading speed would make a noticeable difference.

I also feel the pricing could be more flexible for teams that need only a few advanced features. Better pricing options would make it easier for growing teams to get more value from the platform.

The onboarding experience is fairly straightforward, and there are plenty of learning resources available. However, finding solutions to specific configuration issues can sometimes take time. More practical tutorials and faster support responses would be helpful.

Jira's AI features are a useful addition, especially for summarising issues and helping with repetitive tasks. However, I think they could be more accurate and provide better suggestions based on project context.

Overall, these are relatively small areas for improvement. Jira has been a dependable part of my daily workflow, and a few improvements in usability, performance, and automation could make the experience even better. Review collected by and hosted on G2.com.

What I like best about Jira is its unmatched flexibility in modeling Agile workflows, sprint boards, and release cycles. The UI/UX of modern Scrum and Kanban boards provides clear visual status across complex epics and backlogs. Its integrations ecosystem—seamlessly linking GitHub/GitLab, Confluence, Slack, and CI/CD pipelines—automatically syncs ticket states with pull requests and deployments. Onboarding for new team members is straightforward with standard project templates, while Jira Automation handles repetitive triage without manual overhead. From a pricing and ROI standpoint, it replaces scattered spreadsheets and status meetings, giving engineering and product leadership complete delivery visibility that easily justifies the licensing cost. And the performance of JIRA is very effective. Review collected by and hosted on G2.com.

Jira can quickly become over-engineered and sluggish if not governed by an experienced administrator. The permission schemes, issue type mappings, and custom field configurations are notoriously complex, creating a steep learning curve for non-technical team members. When projects accumulate dozens of required fields and multi-step approval gates, ticket maintenance turns into an administrative chore for developers rather than an enabler of productivity. Review collected by and hosted on G2.com.

I like Jira because it helps me keep development work and technical issues organized throughout a project. I can track ADF pipeline changes, Databricks development tasks, data validation defects, and deployment activities without losing track of priorities. The ticket history is particularly useful when I need to understand an earlier requirement or review the progress of a production issue. I find issue linking, custom filters, dashboards, comments, and workflow tracking particularly useful. Filters help me to identify unresolved defects and pending development tasks, while issue links make it easier to connect related problems, enhancements, and testing activities. It provides several useful views for organizing technical work, including boards and issue lists. It works reliably for everyday task management, issue tracking, and team coordination. It can connect with development repositories, communication platforms, and other project tools. Review collected by and hosted on G2.com.

Some projects have too many ticket fields and workflow stages, which makes updating tasks slower than necessary. Technical requirements can also be difficult to follow when tickets lack clear acceptance criteria or relevant error details. A more consistent approach to ticket documentation would improve the experience. Review collected by and hosted on G2.com.

What I like best about Jira is its flexibility and end-to-end visibility across the software development lifecycle. It helps teams manage requirements, user stories, tasks, bugs, and releases in one centralized platform. Its Agile features, including Scrum boards, Kanban boards, and sprint planning, support efficient project delivery. I particularly value customizable workflows, automation, and dashboards that help track progress, identify blockers, and monitor team performance. As a Technical Lead, Jira helps me coordinate cross-functional teams, manage dependencies, prioritize tasks, and ensure timely delivery. Overall, Jira improves collaboration, transparency, accountability, and productivity. Review collected by and hosted on G2.com.

What I dislike about Jira is that it can become complex and overwhelming when workflows, fields, and dashboards are not configured properly. Performance can sometimes feel slow with large projects, and generating customized reports may require additional effort. Managing notifications and maintaining accurate task updates also requires discipline from team members. Review collected by and hosted on G2.com.

As a developer, what I like best about Jira is having one place to track my sprint work — I always know what’s in progress, what’s Dev Done, and what’s In QA, without chasing updates in chat. The board and filters make it easy to see my open tickets and what I’ve completed in past sprints, which helps in standups and sprint planning. Git integration is a big win: I link branches and commits to Jira tickets, so every change is tied to a story or bug and reviewers can open the ticket from the PR. Ask Rovo(AI) is also very useful — it helps me understand PRDs and ticket context faster, which saves time before I start coding. The UI is simple and clean, so I don’t waste time hunting for what I need day to day. Overall it keeps dev, QA, and release work aligned and makes my sprint workflow smoother. Review collected by and hosted on G2.com.

As a developer, I don’t have major issues with Jira overall — it’s central to how we run sprints. The main frustration is occasional glitches: sometimes I can’t update a ticket status or the ticket won’t open/load until I refresh or try again later. That slows me down during busy days when I’m moving work to Dev Done or QA. I’d also like those UI hiccups to happen less often. Apart from that, day-to-day tracking, boards, and Git linking work well for me. Review collected by and hosted on G2.com.

I like Jira because it makes task management, bug tracking, and project planning much easier. The interface is user-friendly, and the customizable workflows and sprint management features help our team collaborate more smoothly. Overall, it improves transparency across the project and boosts productivity. Review collected by and hosted on G2.com.

Jira can sometimes feel complex and overwhelming because of how many features it includes. The interface isn’t always as intuitive as it could be, and setting up certain configurations and workflows can take more time and effort than necessary. Review collected by and hosted on G2.com.

I find issues linking, workflow transitions, sprint boards, JQL filters, dashboards, and audit history particularly useful. JQL helps me to find specific defects or pending tasks quickly, while issues linking makes it easier to connect a production incident with the development change intended to resolve it. The interface offers several ways to organize and view work, including boards, backlogs, and filtered issues lists. It performs well for day-to-day issues tracking, sprint planning, and team coordination. It works well alongside development and collaboration tools, helping connect issues with code changes, testing activities, and deployment workflows. This is useful when an ETL defect needs to be traced from investigation through code modification, validation, and release. It's a useful tool for maintaining accountability across ETL development and production support. Review collected by and hosted on G2.com.

Jira can become difficult to navigate when projects have too many custom fields, statuses, and workflows. Updating tickets for every small activity can also add administrative work to a developer's day. A simpler workspace with relevant fields makes it much more effective. Review collected by and hosted on G2.com.

The best thing I know about what Jira can do is that it can connect directly or more easily to AI agents. It always finds the information about what you ask and pulls the actual latest status of any topic you are looking for at that moment. I really think that gives it a huge advantage that could keep it at the top. Review collected by and hosted on G2.com.

The most common thing to complain about is that Jira has not been used for that long in my company, a little more than a year. Not all the teams were assigned an account from the beginning, so dealing with access for new members always causes confusion and some delays for new members and teams adopting it. Review collected by and hosted on G2.com.

I like Jira's flexibility and visibility. The ability to customize workflows, dashboards, and issue types makes it easy to adapt to different team needs, while real-time tracking and reporting keep everyone aligned on progress and priorities. Jira's flexibility allows teams to tailor workflows and issue tracking to their specific processes, which makes it easy to use across different projects and teams. The visibility it provides through dashboards and reports helps everyone quickly understand progress, ownership, and blockers, reducing confusion and improving overall efficiency. Review collected by and hosted on G2.com.

While Jira is very powerful, its expensive customization can also make it feel complex at times. There's a learning curve for new users, and simpler tasks may require more configuration than expected. Additionally, managing workflows and permissions can become time-consuming as projects scale. Review collected by and hosted on G2.com.

Jira is very flexible. I can set up Scrum or Kanban boards, break work into epics and tasks, and customize workflows to fit how our team works. The dashboards and sprint reports make it easy to track progress, and the integrations with Confluence, Slack, and GitHub keep everything linked to tickets in one place. Review collected by and hosted on G2.com.

Jira can feel overwhelming at first. With so many settings, custom fields, and workflow options, it takes time to set up properly, and new users often struggle to find their way around. It can also feel slow with large projects, and advanced reporting or JQL queries have a learning curve. Without good admin management, boards can get cluttered quickly. Review collected by and hosted on G2.com.