Jira Service Desk Reviews

What I like most about Jira Service Management is its seamless integration with Jira and its ability to streamline service requests, incident management, and support workflows. It provides a centralized platform for managing customer requests while keeping development and operations teams aligned. Customizable service request and incident workflows. Seamless integration with Jira Software for issue tracking. Self-service portal and knowledge base integration. SLA tracking and automation for timely request resolution. Powerful queues, dashboards, and reporting for support teams. For me, the most valuable feature is the integration with Jira. Support tickets can be easily linked to development tasks and bugs, improving collaboration between support, QA, and engineering teams while ensuring issues are tracked through to resolution. The biggest benefit is improved operational efficiency. It helps teams manage incidents, service requests, and changes in a structured way, leading to faster response times, better visibility, and a more organized support process.

While Jira Service Management is a powerful platform, there are a few things that can be frustrating. The initial setup and configuration can be complex, especially for teams without dedicated Jira administrators. Customizing workflows, request types, and automation rules often requires significant time and expertise. The user interface can feel cluttered, making it difficult for new users to find what they need. Search and filtering aren't always intuitive, particularly when dealing with a large number of tickets. Licensing costs can become expensive as the number of agents and premium features increases. Performance may slow down when working with large projects or complex workflows. For me, the biggest drawback is the administrative complexity. Jira Service Management is highly flexible, but configuring and maintaining it often takes more effort than expected. Simple changes can require multiple configuration steps, making it less approachable for smaller teams.

Jira Service Management solves the problem of managing support requests, incidents, and service operations in a structured and transparent way. Instead of relying on emails or spreadsheets, all requests are tracked in a centralized system with clear ownership and status. Centralizes incident, service request, and change management. Automates ticket routing, approvals, and SLA tracking. Improves collaboration between support, QA, development, and operations teams. Provides complete visibility into ticket status, priorities, and resolution progress. Maintains a history of issues for easier troubleshooting and knowledge sharing. In my day-to-day work, Jira Service Management helps me track production issues, customer-reported bugs, service requests, and operational tasks. It ensures that every request is assigned, prioritized, and followed through to resolution while keeping all stakeholders informed. The biggest benefit is improved operational efficiency. It reduces manual coordination, helps teams meet SLA commitments, and enables faster incident resolution through better collaboration and workflow automation.

I have just finished a massive digital transformation project for a leisure cruise travel client, where we orchestrated changes across Salesforce and Couchbase, as well as a legacy IBM Mainframe and a Snowflake database. Jira Service Management was the glue that held our overall delivery and time tracking together across a multi-vendor, multi-continental team.

Creating Epics, Stories, Defects, and spikes effortlessly, along with backlog grooming, really supported our scrum team (and eventually our scrum-of-scrums team). The ability to create defects and link them to Stories and the relevant Epics helped us track delivery quality and gave leadership clearer feedback on code quality. JIRA also provided strong insights for high-level leadership, with the visibility they needed to analyze overall team velocity and spot multi-vendor bottlenecks ahead of time.

I’ve been using JIRA for the past few years, and so far I haven’t run into any issues with it. I haven’t had problems with pricing or with creating workflows—everything has worked perfectly fine for me.

Its intuitive ticket management, workflow automation, customizable service desks, and integration with the Atlassian ecosystem make it an efficient platform for managing IT service and support operations

The learning curve is steep, advanced customization can be complicated, and the interface can feel cluttered for new users. Costs can also add up as more users and premium features are needed

It streamlines ticket management, automates repetitive support tasks, and improves visibility into service requests. This helps our team resolve issues faster, stay organized, and deliver better support to end users.

Task & Issue Tracking – Easy to create, assign, and monitor tasks, bugs, and user stories.

Visibility & Transparency – Real-time tracking helps everyone see project status, blockers, and ownership.

Complex Configuration – Setting up workflows, permissions, and custom fields can require significant admin effort.

Real-time dashboards and progress tracking.

.Excellent Platform for Tracking incidents, and automating tasks which saves time

As a new user, Initially I faced challenges in making dashboard understanding the navigations, understanding the difference between scrums and kanbans

Integrate seamlessly with other tools like

We have been using Jira software for a couple of years now, and it has helped us a lot, especially with task optimisation, clearer pipelines, and better resource allocation. In short, I’d put it this way: project management without Jira wouldn’t be possible for us, especially with their AI power tool.

I believe the pricing can be much better, and sometimes we feel lag when it comes to shifting the view of tiles, so that is something which we don’t like, but otherwise, I feel I mean the premium or the premium pricing can be little more better

I mean, like every other business, one thing which is scattered data and scattered request that has one thing which

I appreciate using Jira Service Management for task management and its ability to view progress in real time. The Kanban view, which allows me to see task status for the whole team, is really helpful. My daily work focuses a lot on delegating tasks to my team, so watching them close the tasks out with criteria is really beneficial.

Overall ease of use for new users, especially the need for better training on basics and quick tour guides.

I use Jira Service Management for managing tasks and projects, including sprint planning. The Kanban boards help me see the status of tasks across the whole team. It aids in task delegation, allowing me to track closures based on criteria.

What I like best about Jira Service Management is that I don’t have to keep following up on emails to know what’s happening with my request. Whenever I raise a ticket, I can easily check the status and see updates in one place. It’s pretty straightforward to use, even for someone who isn’t from a technical background. I also like that nothing gets lost in long email chains anymore. It has made it much easier for me to reach the right team and get issues resolved faster.

when you’re trying to find specific information, especially if there are a lot of tickets and updates. The interface has many options, which is useful, but for occasional users it can take some time to figure out where everything is. Also, some notifications can be repetitive, and I end up receiving more emails than I really need.

For this i just have one word which is efficiency, efficiency because more structured way and having visibility of everything you need

I use Jira Service Management to handle our day-to-day IT requests, employee access requests, system issues, project tracking, and visibility. I find that efficiency is the most important thing Jira Service Management provides. I like how easy it is to work on day-to-day tasks. The integration with other platforms is quite easy, keeping everyone on the same page. For example, receiving updates or alerts about any ticket or project on Slack makes life super easy.

A couple of things come to mind. First, some configuration and permissions can be harder to understand than they need to be, especially when you are setting up a new project or request type. A simpler and more intuitive permission structure would help. At times, it can be difficult to understand why certain users can or cannot access specific projects. It was quite challenging initially.

Jira Service Management enhances efficiency, making day-to-day tasks easier. Integration with other platforms keeps everyone on the same page, simplifying updates and alerts, particularly through Slack.

JIRA Service Management is really valuable for tracking issues, sharing updates, collaborating with theinternal support team responsible for resolving problems, and we can document the incidents for knowledge management. By using JIRA JSM as the Blue Yonder Product teams internal Ticketing system, we saw a noticeable improvements in our Mean Time to Resolution (MTTR) and Service Level Agreements (SLAs), which resulted in increased operational efficiency when addressing issues.

Renewal costs, and customers sometimes face obstacles when it comes to tools integration. Furthermore, the Atlassian JIRA support team could improve their assistance to users by undergoing more formal training.

In Blue Yonder, we completely rely on JIRA Service Management Tool to manage the IT infrastructure and application Support team Incidents, and we also use it to assign user stories and tasks to our internal support teams across different projects.