Jira Service Management

What do you like best about the product?

What I like best about Jira Service Management is how it brings every request into one organised place. Customers raise tickets through a simple portal, and our team can track, prioritise, and resolve them without anything getting lost in email threads.

The automation rules save real time by routing tickets, assigning owners, and sending updates on their own. It also connects smoothly with Jira, Confluence, and Slack, so the work flows between teams without extra effort.

The queues and SLA tracking give us a clear view of what needs attention first, and the knowledge base cuts down repeat questions. The AI-powered suggestions help with summaries and request handling. Setup is straightforward, and support resources are easy to find.

For the price, the structure and visibility it brings make it a strong return on the investment.

What do you dislike about the product?

Jira Service Management is a capable platform, but a few areas could be smoother. The interface can feel busy for new users, with many settings and options, so it takes time to find your way around.

Setup and onboarding need some planning. Configuring workflows, queues, and automation rules is flexible but takes effort, especially for teams without a dedicated admin. Pricing also climbs as you add agents and unlock advanced features, which makes budgeting harder as the team grows.

Reporting works well for the basics, but building custom reports takes extra steps.

Minor points overall, and nothing that takes away from the value it delivers.

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

Jira Service Management solves the problem of requests getting lost across email, chat, and spreadsheets. Before, it was hard to see who owned what, and response times slipped whenever volume went up.

Now every request lands in one place, gets routed automatically, and is tracked against clear service levels. Tickets are picked up quickly and the platform stays fast and reliable even when the queue is busy, so the team spends less time chasing updates and more time resolving issues.

The benefit is faster response times, better visibility, and a smoother experience for the people raising requests.

What do you like best about the product?

The best part for us is how easily it connects with our existing Jira projects and Bitbucket repos. When someone opens an internal infra or IT request, we can link it straight to engineering tickets without switching tools. The REST API is also solid for automating ticket updates from our scripts.

What do you dislike about the product?

Setting up custom workflows and permission schemes in the admin UI is still way too confusing and takes too many clicks. The interface can also feel pretty slow and heavy when loading large queues, and the per-agent pricing adds up fast as the team grows.

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

We use it to track internal DevOps and IT requests like server access, EDA license provisioning, and new hire onboarding in one place instead of losing messages in Slack threads. It keeps our response times down and makes it easy for new engineers to find past issues or request access on their own.

What do you like best about the product?

I use Jira Service Management to centralize requests and secure exchanges with teams. It has structured our financial processes and provides complete traceability of our daily flows, instead of scattered requests via messaging. I love that the tool is smooth, simple, and efficient, allowing the creation of tickets with the help of Rovo, its integrated AI agent, and providing an overview of the company's request types. I can also process and track payment requests, manage authorizations and governance of our TMS, as well as requests for Spendesk company cards, passenger billing, and CRT. The installation was simple, quick, and efficient, and the teams were able to quickly familiarize themselves with the tool.

What do you dislike about the product?

I find it takes a few clicks to find the tickets I just created and their history. It's not always intuitive or simple. A global dashboard upon entering Jira Service Management could improve this.

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

I use Jira Service Management to secure exchanges with teams around emergencies, sensitive access requests, and supporting documents. It structures our financial processes, eliminates disorganized solicitations via messaging, and ensures complete traceability of our daily flows.

What do you like best about the product?

Jira Service Management provides excellent visibility and traceability across the issue lifecycle. I particularly value its customizable workflows, automation capabilities, and seamless integration with Jira Software, which simplify defect tracking, cross-team collaboration, and QA process management. It helps improve accountability, streamline issue resolution, and maintain transparency across releases.

What do you dislike about the product?

Some advanced configurations, workflow customizations, and automation rules can be complex to set up and maintain. The interface can also feel overwhelming when managing multiple projects, and reporting capabilities could be more flexible for deeper insights into team performance and issue resolution trends.

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

Jira Service Management helps centralize defect tracking, service requests, and issue management across teams. It provides clear visibility into issue status, ownership, and resolution progress. As an SDET, it helps me streamline QA coordination, track blockers, collaborate effectively with developers, and ensure issues are resolved within release timelines. This improves accountability, traceability, and overall release quality.

What do you like best about the product?

I like Jira Service Management’s rich JQL support and simple interface. Story points carrying forward is good, and customer issue tracking is great.

What do you dislike about the product?

Project management doesn’t feel native to Jira Service Management, and it feels off. Its AI integrations aren’t up to industry standards. I also can’t create issues from Slack threads and assign them to different people or cycles like I can in Linear.

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

I use Jira Service Management to track issues and bugs, manage engineers’ sprint cycles and customer escalations, and manage development cycles for feature and maintenance work.