Jira

What do you like best about the product?

Jira provides great visibility into the progress of the projects using workflows, Scrum boards, Kanban boards, sprint planning, and reporting. User stories, bugs, tasks, and releases become easy to track, while at the same time, all team members stay aligned. It works seamlessly with the development environment, such as Git repositories, CI/CD pipelines, and documentation platforms. Dashboards and filters in Jira have great flexibility, which makes it easy to monitor KPIs, sprint health, and overall performance of the team.

What do you dislike about the product?

It has a steep learning curve, particularly for those who are new or not technical. Workflows, permissions, and issue types need to be configured carefully; otherwise, projects and backlogs become cluttered. Some reporting and automation features are available only for the premium plan.

What problems is the product solving and how is that benefiting you?

Jira substitutes for the spreadsheets and emails in which projects were tracked previously. It helps to increase transparency, providing stakeholders with the visibility of the status of projects. It improves communication between product teams and development, and helps to prioritize work. With the help of the automated workflows, repetitive administrative tasks become automated.

What do you like best about the product?

What I like most about Jira is how effectively it manages the full bug lifecycle. I use it every day to log defects, track their progress, assign issues, add comments, attach screenshots and logs, and collaborate with developers until each issue is resolved. Keeping everything related to a bug in one place makes coordination and follow-up much easier.

I also appreciate how well Jira supports Agile workflows. Being able to manage user stories, tasks, bugs, and sprint activities within a single platform helps the whole team stay aligned. The search filters, dashboards, and reporting tools are especially helpful for monitoring progress and quickly finding the details I need.

Overall, Jira has become an essential part of my daily work. It keeps defect tracking organized, strengthens communication between QA and development, and provides clear visibility into the status of every issue.

What do you dislike about the product?

I don’t have any major complaints, but the interface can feel overwhelming at times, especially for new users. With so many features, screens, and configuration options, it takes a while to get comfortable and become familiar with the platform.

I’ve also found that setting up advanced filters or customized dashboards comes with a learning curve. They’re powerful once configured, but they aren’t always intuitive if you only use them occasionally.

Aside from these minor points, Jira has been reliable for managing defects and supporting Agile development across the project lifecycle.

What problems is the product solving and how is that benefiting you?

Jira helps me manage software development work and track defects in a structured, organized way. I use it to log bugs, follow their progress through different stages, collaborate with developers, and verify fixes before closing issues. Rather than handling defects through emails or spreadsheets, everything stays in one place with full history, clear visibility, and better accountability.

It also supports sprint planning by keeping user stories, tasks, and bug fixes together, which makes priorities and release progress easier to understand. Having comments, attachments, and status updates tied directly to each issue improves communication and reduces back-and-forth across the team.

The biggest benefit for me is stronger collaboration and traceability. Jira keeps the entire bug lifecycle consistent, reduces confusion, and makes it straightforward to track each issue from the moment it’s reported through resolution and final verification.

What do you like best about the product?

Jira is very useful for managing time and tracking tickets and work, including logging time. JIRA’s user-friendly UI really stands out compared with competitors like Microsoft ADO, etc.

What do you dislike about the product?

If you enable too much feature, UI become messy, also for a new user, navigating between tickets etc can be hard.

What problems is the product solving and how is that benefiting you?

JIRA solves our problem by helping us to plan our sprint. we can tag the user stories to current sprint, log our time, QA can log bugs, BA can give inputs, stakeholders can see the progress and team involvement in real time thus making everything smooth and efficient

What do you like best about the product?

The ability to maintain swim lanes, and the tickets on Sprint boards, and the ability to bulk move the tickets around on the board and across users.

What do you dislike about the product?

The lack of accuracy in third party integrations, like inability to manually link PRs to a ticket when the PR ID for commit message doesn't match the Jira ticket ID.

What problems is the product solving and how is that benefiting you?

Management of the features, and release targets for those features.

It helps in finding out the responsible person for a feature with ease, and defining work done in a specific period of time.

What do you like best about the product?

Jira has helped our team standardize and streamline our support operations. I appreciate how flexible it is for setting up workflows, automations, custom fields, and SLAs that align with different business requirements. The service portal is straightforward for users to navigate, and its integration with other Atlassian products makes collaboration much smoother across the team. While there’s a learning curve at the start, once it’s configured properly it becomes a dependable platform for managing day-to-day service requests and broader operational processes.

What do you dislike about the product?

Some of the more advanced configuration options take time to understand, especially for new administrators. The automation limits on lower-tier plans can also feel restrictive for larger teams running more complex workflows. The reporting and dashboards are helpful overall, but I’d like to see more built-in reporting options so I don’t have to rely as much on additional apps or custom configurations. A few administrative tasks could also be streamlined to cut down on setup time.

What problems is the product solving and how is that benefiting you?

Jira helps us manage service requests, incidents, changes, and internal projects from a single platform. We use it to automate repetitive tasks, enforce SLAs, and standardize workflows across teams, which keeps our processes more consistent. It has also improved visibility into ongoing work through dashboards and reporting, making it easier to prioritize requests, track progress, and collaborate across groups. Since moving from our previous ticketing system, we’ve reduced manual effort and maintained more consistent support operations overall.