Jira Reviews & Product Details

What I like best about Jira is its ability to organise work, track project progress, and improve collaboration across teams. It provides a centralised platform where tasks can be created, assigned, prioritised, and monitored throughout their lifecycle. I particularly appreciate the Scrum and Kanban boards, sprint planning, backlog management, and reporting features, which make it easier to manage workloads, track deadlines, and identify bottlenecks. Jira also integrates well with other development tools, making it suitable for software development teams working in an Agile environment. Overall, it improves transparency, accountability, and team productivity. Review collected by and hosted on G2.com.

One thing I dislike about Jira is that it can feel complicated for new users, especially for people who aren’t familiar with Agile project management methodologies. It offers a wide range of features and configuration options, but that can make the initial setup and day-to-day navigation overwhelming. Customising workflows, managing permissions, and setting up dashboards can also require a fair amount of technical knowledge, which adds to the learning curve. On top of that, some advanced features and integrations are only available on paid plans, which may drive up costs as an organisation grows. I’d also like to see a simpler, more intuitive interface, along with better performance when working with large projects and sizeable backlogs. Review collected by and hosted on G2.com.

I use Jira to track work, log time, document what I do, and assign work items to myself so I can show what I did. It helps me with metrics, including how many days I’ve spent on a work item. I like the UI and the connectivity with apps like GitHub and Slack. The user experience is very good, and it’s understandable for new users. When I create a branch, PR, or commit in GitHub using the Jira ticket name, Jira shows the related Git items in the ticket’s development section. That makes it much easier to track PRs and branches in Jira instead of searching in GitHub. I also get updates about my assigned and watched tickets in Slack through the Jira bot. It was easy for me to set up as a developer. Review collected by and hosted on G2.com.

I have some latency issues in Jira. If I leave a page idle and come back, I have to reload to see updates. If someone changes a ticket while I’m away, I can’t see the change immediately or even tell that it happened, so I have to rely on email updates. Review collected by and hosted on G2.com.

I like that Jira gives me a clear view of work assigned to me and the progress of different sales and marketing activities. I can check priorities, deadlines, task owners, and updates in one place. It has also helped me to understand how longer teams organize and track their day-to-day work. The board and task tracking features are my favorite. Being able to see tasks moving from 'To Do' to 'In Progress' and then 'Completed' gives me a quick understanding of the team's workload and helps me manage my own priorities. The interface is organized and good, with visibility into tasks. It takes some initial learning for someone from a sales or marketing background, but it has been reliable for my regular work. I can create or update tasks, add comments, check deadlines, and follow team progress without major issues. It works well for keeping track of multiple activities at the same time. Review collected by and hosted on G2.com.

Jira can feel a little complicated when you are new to it. There are many options for issue types, statuses, fields, and workflows, so it took me some time to understand how everything fits together. For simple tasks, the number of steps can sometimes feel unnecessary. Review collected by and hosted on G2.com.

I don't really like Jira, but I do find it easy to use, correct, and organize. I can organize sections for different departments and countries, and keep each case within the same client's. I can also connect the mail through Outlook and see how it enters the DIDA account. I can quickly see what fails and what doesn't. Review collected by and hosted on G2.com.

4 or 5 years ago, integrating photos or documents was a disaster: they didn't integrate well and the client didn't receive them. At first, it was also hard for me. Now I don't know well, but it has improved a lot and is lighter. Review collected by and hosted on G2.com.

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.

1. AI-Powered Work Assistance 2. Rovo AI Search and Knowledge Discovery 3. Better Cross-Team Planning Review collected by and hosted on G2.com.

1. Simplicity and Ease of Use Jira's flexibility is both a strength and a weakness. New users can feel overwhelmed by projects, issue types, workflows, screens, custom fields, and permissions. Different teams often configure Jira differently, making it harder to move between projects. A more opinionated, simpler default experience could reduce the learning curve. 2. Configuration Complexity Many organizations end up with: Hundreds of custom fields Numerous workflow variants Complex automation rules Over time, Jira instances can become difficult to maintain. Better governance tools and AI-driven cleanup recommendations would help administrators keep systems healthy. 3. Search and Reporting Jira's search is powerful, but it often requires knowledge of filters and query syntax. Users frequently want to ask: "What's blocking this release?" "Which high-priority items are at risk?" "Where are we missing owners?" Natural-language analytics could make reporting much more accessible. 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.