JIRA Service Management Reviews

The default settings for Jira Service Management allow you to maximize its potential right away, with nothing in the way of setup. It is possible to personalize it with a wide variety of settings so that it functions just how one would like it to.

Because our SSO implementation needs it, in order for a user to sign into the customer portal, they will first need to sign into the parent Jira site.

I find the UI of Jira Service Desk very clean and modern compared to other service desks software on the market. Included with the service desk is a customisable user-facing portal for users to raise tickets in, which proved very popular with staff when raising tickets alongside traditional email tickets. Due to the way Jira splits service desks into different projects, we were able to create service desks for other departments in the organisation which helped improve productivity and workflow. There are some very useful and well-designed default reports included for ticket statistics (which can be used to keep management happy!). We found the default setup of Jira Service Desk fit our needs very well, but it is very easy to customise ticket workflows and other features to suit more complex needs.

For a service desk technician using Jira Service Desk the back-end UI for managing tickets can be a little overwhelming, however this can be fixed by editing the default workflows for tickets to hide not required information and details. The administration settings are somewhat unintuitively set out for system administrators, but once you get to grips with the layout it becomes easy enough to find what you need from the settings page. We found the instructions on the Atlassian website for setting up an external redirect with a custom URL in IIS a little sparse on detail, but a quick trip to the Atlassian forums cleared up any queries we had with the process.

Most important functions, from perspective of scrum or devops team member, can be learn quickly and used easily. Also it gives a lot of option of organizing workflow between many agile teams. You can have different levels of tasks - and visualizations to them. I like that you can organize many boards and link everything. It takes of course a little bit of consistency in following the rules in order to not create a mess.

Well, it tends to have sudden downtime.. for no reason (well at least from my perspective) it’s not responding. Speed interface could be improved. Sometimes you have to wait a while after an action performed.

Jira is a good tool , we used it mostly for Product Management based work due to it's easy to share and easy to grant access features I find it ideal in a Product based environment and that is where it shines best . (decent pricing , good collaboration , good reporting )

At this price point , you have a lot of variety and the market becomes very competitive , you can go other options if you have a Support department for example , if money is no option than this can also fit that role , however the additional features that Jira offers I feel might be lost on support.Summary : Great for Product , Medium for Support

Estimating the team's velocity can be pretty accurate when the users fill in their Story Points and the time to completion. Cards also provide a lot of information, team members can collaborate in the comments section and the ability to create sub-tasks is a big plus.

Jira can become overwhelming for newcomers, specially if there are no explicit policies on how to use it. Also, when marking tasks as Done, it feels the completion time fields are a bit redundant.

Jira Service Desk was very easy to get started with. You could literally sign up for it and begin using it within an hour. Ticketing system is very customizable and powerful. Customers can be added in bulk and customers can sign up for entering issues. We were able to create different projects (or service queues) so that customers could send requests for IT help, or administrative help, or help with projects. Each such project/queue had different fields. Metrics are all built into the software, so we can know how often Service Level Agreements were breached, who breached them etc. The sheer amount of customizability is a joy. However, without discipline and thoughtfulness, it is very easy to customize it the wrong way.

We feel that the price point could be lower and the speed could be a little faster. Atlassian has made improvements with speed. If a company had 5 people manning different queues and the issue volume is low, the cost would be ~1500/year for those 5 users. So, it would may not be cost effective for a small company that is watching their costs closely. We also felt that a Wiki is not built in. So, if a common solution needs to documented that spans multiple tickets, there's no way to do so. We could buy Confluence from Atlassian for an additional cost.

JIRA Service Management is a powerful tool that enables teams to customize workflows, processes, and reports according to their unique requirements. It seamlessly integrates with JIRA, allowing teams to easily switch between project and service management workflows while sharing information. The collaboration capabilities of JIRA Service Management are exceptional, as teams can use comments, usernames, and attachments to communicate with each other, ensuring that everyone is up-to-date on critical updates. Automation is another impressive feature that saves a team's time and improves efficiency. Teams can set up automation to automatically route tickets to the appropriate team members, send customer notifications, and update ticket status.Furthermore, JIRA Service Management provides comprehensive reporting and analytics capabilities to help teams track essential metrics and identify areas for improvement. Reports can track response times, resolution times, and customer satisfaction scores, among other things. JIRA Service Management is an invaluable tool that streamlines service management processes and enhances customer satisfaction.

Limited Mobile App Functionality: While JIRA Service Management offers a mobile app, some users have reported its limited functionality compared to the desktop version. This limitation can make it difficult for teams to manage service requests on the go.

Jira Service Management itself, is a robust service management tool that offers a wide range of features and capabilities. Some of its key strengths include its flexibility and scalability, which make it an ideal choice for businesses of all sizes. It also offers powerful automation capabilities, allowing users to streamline their workflows and improve productivity. In addition, Jira Service Management provides detailed analytics and reporting tools, giving users valuable insights into their service operations.

Of course, like any software tool, Jira Service Management has some potential downsides. For example, some users have reported that it can be difficult to set up and configure initially, especially for organizations with complex workflows or service structures. Additionally, some users have found the interface to be somewhat complex and overwhelming at first, although with time and experience, most users find it becomes more intuitive.

- High Control
- Wide choices of features
- Confluence Integration
- Very rich suite of addons on premise version...

- ...which requires extra costs
- Some features are too basic and pretty much requires addons
- Learning Curve for admin requires effort

JIRA Service Management offers robust reporting and analytics capabilities, providing insights into support team performance, ticket trends, and customer satisfaction levels. These metrics help organizations identify areas for improvement and make data-driven decisions to enhance their support processes.

Due to its extensive functionality and customizable nature, there can be a learning curve associated with mastering JIRA Service Management. Administrators and users may need time to understand the platform's features and optimize its use for their specific requirements.

Easy use for the agents (help desk consultants) is why we decided on this tool. The ability to connect tasks to our regular projects in Jira Software is another winner feature because it saves a lot of time and allows better communication between teams.

The major downside to Jira Service Desk is customizing it. I don't know if anyone uses it straight out of the box, but for us, it was necessary to spend a couple of days customizing workflows, screens, and general settings.Another rather annoying thing is the vagueness of the agents' assignments which determines how much we pay for licenses.

Jira service management is one of the best service desk softwares in the market. The ease of use is great, even for users new to the software. It helps the users keep a proper and clean track of the incidents/tasks/etc they have. One of the best things about Jira Service Management is that multiple teams can easily collaborate and work on it. This enables big projects involving various teams to work seamlessly.

There are not many major disadvantages with using this Jira Service Management software. But a user must be careful while deciding to delete a ticket, because once deleted it is goodbye for ever. It cannot be retrieved. This option can be modified to allow retrieval of deleted tickets to ease the process for users who might delete important tickets unintentionally.

Jira Service desk works great. We use it in a media company in all of the service departments to track requests from Media ingest, to graphic requests, to crew requests. Our producers can easily log in from anywhere and fill out customized forms for the type of service they are looking for. The department gets the request in seconds and can start fulfilling it right away. In a fast pace news world, this allows us to get what is needed for broadcast air done fast while keeping track of all the work we have to do.

There are some features that you would think would come right out of the box with jira service desk that doesn't. The only way to get them is to buy a plug-in from their market place. Some features that we would like to see is having the requester see who is assigned the order & allow them to request updates to their requests.

It's the best tool for project management I have worked with. It's best at tracking progress of user stories and tasks, but works well also as a ticketing system and time tracking application. It is easy to track multiple projects at once thank to a possibility to create dashboards and groups for each of them. It can also be integrated with confluence in order implement an integrated knowledge base.

The text editor could be improved, as well as some features could be implemented to make the user stories and filtering management a bit more user-friendly and provide better user experience.