Try our new research platform with insights from 80,000+ expert users
Head of ALM at a tech services company with 1,001-5,000 employees
Real User
It's a good solution at a reasonable price, and it's quicker to implement inside a company, but support is subpar
Pros and Cons
  • "Service Management is great if you're an Atlassian shop already using JIRA for the development team and you want another tool for help desk ticketing. When it's all under the same umbrella, I can easily take a ticket from the help desk and move it to the development team. You can't beat that integration between two products."
  • "I rate Atlassian support two out of 10. It takes a lot of time to reach them and get ahold of someone who understands my problem enough to provide a solution. Also, I live in Israel, so my work week is Sunday through Thursday, but I can only contact them from Monday to Wednesday."

What is our primary use case?

My clients use Service Management for general ITSM ticketing. They typically use Jira internally for providing help desk services to other departments, but one of my customers uses it for his customers, like external websites, etc.

What is most valuable?

Service Management is great if you're an Atlassian shop already using JIRA for the development team and you want another tool for help desk ticketing. When it's all under the same umbrella, I can easily take a ticket from the help desk and move it to the development team. You can't beat that integration between two products. 

What needs improvement?

Service Management is highly customizable, but I think it might be too customizable. If a company isn't aware of the best practices, it can easily mess something up. For example, you might try automating something that Jira doesn't support, and it could interfere with the product's out-of-the-box capabilities. 

Asset management should be built into Service Management. Typically, companies need both. You have to buy Atlassian's asset management solution separately. It could either be offered as a bundle or some lighter version of asset management could be included with Service Management. 

For how long have I used the solution?

I have been using Jira Service Management for a year or so.

Buyer's Guide
JIRA Service Management
February 2025
Learn what your peers think about JIRA Service Management. Get advice and tips from experienced pros sharing their opinions. Updated: February 2025.
837,501 professionals have used our research since 2012.

What do I think about the stability of the solution?

I have confidence in Service Management. 

What do I think about the scalability of the solution?

Service Management is scalable. 

How are customer service and support?

I rate Atlassian support two out of 10. It takes a lot of time to reach them and get ahold of someone who understands my problem enough to provide a solution. Also, I live in Israel, so my work week is Sunday through Thursday, but I can only contact them from Monday to Wednesday.

How would you rate customer service and support?

Negative

Which solution did I use previously and why did I switch?

I've worked with ServiceNow. Comparatively, Jira provides a good solution at a reasonable price, and it's quicker to implement inside a company. ServiceNow's implementation is complex. I'm more comfortable with Jira. 

How was the initial setup?

I rate Service Management six out of 10 for ease of setup. At first, setting up Service Management seems incredibly easy. You log into the website and access the site, but nothing comes from the backend because you don't have anything set up for the company. You need to set up the fields, workflows, etc. Companies expect to be able to do it fast after buying the license, but it's not that quick. It typically takes five days to set it up. It isn't a plug-and-play solution.

What's my experience with pricing, setup cost, and licensing?

I rate Service Management four out of 10 for affordability. The price could be better, especially for companies using more than one Atlassian product. It's suitable for SMBs that can afford it. I don't think there's another tool that's both better and cheaper. All help desk tools are relatively expensive.

You also need to consider the overall work we need to do on the tool. The five days of work needed for deployment isn't much, but it requires ongoing maintenance over time.

What other advice do I have?

I rate Jira Service Management seven out of 10. If you plan to implement Service Management, you need to be aware that you can do whatever you want with it, but you might not know the long-term effects. If you do too much automation, it could have unforeseen consequences in the long run. You need to be highly specific about your needs from the start, so you can correctly build the tool's architecture.

Disclosure: My company has a business relationship with this vendor other than being a customer: Integrator
PeerSpot user
reviewer1097934 - PeerSpot reviewer
Director at a financial services firm with 1,001-5,000 employees
Real User
Beneficial for tracking issues with the development side
Pros and Cons
  • "Useful for tracking issues with development."
  • "Auditing team uses this solution to track audit findings and follow-up."
  • "Cost has prohibited us from switching entirely to this solution."

What is our primary use case?

In our bank, we use a partner company who develops software for us. They use Jira for the developer portion to track issues, or bugs, that need to be fixed on the software development life cycle. 

We have two teams, one is the development department which includes developers and business analysts who use Jira to track and develop issues within their own team and a third-party consultant. The other is the audit team who is using Jira to track their audit findings and follow-up.

What is most valuable?

Jira's issue tracking for different projects for the development side is quite useful.

What needs improvement?

With respect to our help desk, we have been considering switching from ManageEngine to Jira so that we can have a single consolidated system for all the development life cycles. Jira has different modules that can develop workflow for demand management and project management, but the solution is no out of the box and would require lots of customization. The cost of switching has prohibited us from moving ahead with Jira as a service desk solution.

For how long have I used the solution?

I have been using Jira Service Management for almost 5 years.

What do I think about the stability of the solution?

Jira is quite stable.

What do I think about the scalability of the solution?

We haven't used Jira on a large scale. Our work groups are a maximum of 20 people.

Which solution did I use previously and why did I switch?

We currently are using ManageEngine for the service desk solution. This solution has been good but they do not have a consolidated system for the development life cycle. We would like to switch to Jira for this service solution as well but cost prohibits us from moving forward.

How was the initial setup?

The initial setup is not complex. The deployment itself does not take much time, however the custom workflow does take longer. 

What about the implementation team?

We completed the installation with the help of external consultants who are familiar with Jira.

What other advice do I have?

Jira is becoming quite popular and is well supported. We find that when working with other companies on other projects, they are using Jira to track issues so it is beneficial for us to use the same solution.

Jira has lots of modules and integrations, however too many makes licensing difficult to understand upfront and becomes quite expensive to have a full solution.

I would rate Jira Service Management a 9 out of 10.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
JIRA Service Management
February 2025
Learn what your peers think about JIRA Service Management. Get advice and tips from experienced pros sharing their opinions. Updated: February 2025.
837,501 professionals have used our research since 2012.
Platform Scrum Master at a comms service provider with 5,001-10,000 employees
Real User
Great reporting and customized forms options; lacks capability to see all Jira tickets
Pros and Cons
  • "Great to be able to create customized forms."
  • "When you raise a ticket with Jira, there's no ability to see your other JIRA tickets."

What is our primary use case?

Our primary use case is for customer service and customer requests. We also use it to set SLAs and as a general help desk. We are customers of Jira.

How has it helped my organization?

The solution has improved company functioning by providing more transparency, in my opinion. Our business is already working out of JIRA, so it connected directly with the platform rather than requiring us to move between several different platforms.

What is most valuable?

The reporting is a great feature. I also like being able to create customized forms which is extremely helpful.

What needs improvement?

If you raise a ticket with Jira, the portal doesn't enable any capability to see your other JIRA tickets, only the parts that are in the plugin for the service management. That's not a great experience because we have project teams that work out of their own Jira backlogs, so unless it's a link to a ticket in the JSM, there's no visibility for the customer in one single location.

For how long have I used the solution?

I've been using this solution for two years. 

What do I think about the stability of the solution?

We haven't had any issues with performance, other than issues related to being on-prem. It's a stable solution.

What do I think about the scalability of the solution?

The biggest issue is not being able to display linked issues and that makes scalability painful as far as the customer experience goes, and weighs down the system with more tickets. In terms of expanding, it's fairly straightforward. We have over 5,000 users in various roles including managers, developers, HR - it's across the board. In terms of maintenance, we have the main administrator and then a couple of guys that help out.

Which solution did I use previously and why did I switch?

We transitioned from Salesforce to Jira Service Management mainly because a lot of our teams were already working out of Jira for their own project tracking. It just allowed us to bring everything together rather than working in different systems.

How was the initial setup?

The initial setup was fairly straightforward and was carried out by an in-house team.

What other advice do I have?

I would suggest looking into your current layout and requirements, evaluating them and then figuring out the best option in terms of how you want things categorized and broken down from both a customer perspective and a backend perspective before you try to build it out.

Despite the few downfalls, its cost is still very good compared to other holistic systems. A big reason for getting the switch approved was that the cost was substantially lower than other solutions. I can't speak for the cloud experience, I'm sure it's a little easier than running on-prem, which is very administrator heavy when you want to do a lot of automation or post functions. It's important to be prepared for that. Depending on how your organization is set up, you're likely to need your admin to do those things.

I rate the solution seven out of 10. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Francesco Fiorentini - PeerSpot reviewer
Bis Development Lead at a manufacturing company with 51-200 employees
Real User
Top 10
User-friendly and can be used for change of management
Pros and Cons
  • "JIRA Service Management is a very user-friendly solution."
  • "JIRA Service Management could include more AI features."

What is our primary use case?

We are using JIRA Service Management for change of management.

What is most valuable?

JIRA Service Management is a very user-friendly solution.

What needs improvement?

JIRA Service Management could include more AI features.

For how long have I used the solution?

I have been using JIRA Service Management for one year.

What do I think about the stability of the solution?

JIRA Service Management is a very stable solution.

I rate the solution an eight or nine out of ten for stability.

What do I think about the scalability of the solution?

Around 50 users are using JIRA Service Management in our organization on a daily basis.

I rate the solution an eight or nine out of ten for scalability.

What other advice do I have?

I would recommend JIRA Service Management to other users.

Overall, I rate the solution an eight or nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Anuj-Kataria - PeerSpot reviewer
QA Manager at Next Solutions
MSP
Top 5Leaderboard
Provides great management features with a simple deployment process
Pros and Cons
  • "Provides excellent management features."
  • "Generally requires the purchase of additional plugins."

What is our primary use case?

We are a services-based organization providing software services to our customers.

What is most valuable?

This product is great at providing end-to-end project management for creating dashboards, for test case management, bug defect management, and the like. The management aspect is a key valuable feature. 

What needs improvement?

I think test case management could be more efficient. It currently requires two plugins which makes it less effective. At the moment with Jira, there are various products not included in the license such as CI CD pipeline or Atlassian Bamboo. Even if you take a bundle, these products are considered separate. On the other hand, if you buy an enterprise version of Microsoft Azure DevOps, a competitor of Jira, it's a one-stop solution on a single platform. 

For how long have I used the solution?

I've been using this solution for over 10 years.

What do I think about the stability of the solution?

The solution is stable. 

What do I think about the scalability of the solution?

The scalability is good. 

How are customer service and support?

We don't use the technical support very much. Jira provides good documentation. 

How was the initial setup?

Jira's advantage is in the straightforward set up. It's very easy in comparison to other tools. Deployment generally takes two to three weeks before we can go live. We use a third party for our deployments. The infrastructure environments vary from client to client. The deployment requires testers, developers, a technical architect, as well as project and service managers. 

What's my experience with pricing, setup cost, and licensing?

The cost of the product is not very expensive but if you need to buy other plugins such as Confluence, it costs extra. I would recommend choosing a bundle option, if Atlassian gives you that option with Jira Confluence.

Which other solutions did I evaluate?

We also deploy Microsoft Azure DevOps. The client generally decides which solution they want to go with. The added advantage with Microsoft is that it's a one-stop solution whereas Jira's benefit is that it offers a less expensive product. 

What other advice do I have?

I rate this solution eight out of 10. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer1513458 - PeerSpot reviewer
IT Director at a real estate/law firm with 1,001-5,000 employees
Real User
The best option on the market that is easy to set up and offers good service management
Pros and Cons
  • "The initial setup is easy and straightforward."
  • "The solution needs to be integrated better with Office X5."

What is our primary use case?

The solution is mainly used for testing the product. It's for managing the team and the BI team among others.

What is most valuable?

The service management aspect of the solution is excellent.

The solution has good cloning capabilities. Our team was happy with it.

The initial setup is easy and straightforward. 

Overall, it's the best option on the market, after looking at other products.

What needs improvement?

The solution needs to be integrated better with Office X5. We use that often and need Jira to be able to effectively communicate it.

Right now, my judgment of the solution is based on their trial version. I haven't likely experienced the full functionality and features that are already there. That's why I cannot give you the highest measurement for performance. A paid version may have much more to offer clients.

I haven't experienced asset management within the product. In the IT field, assets are the biggest issue for the life cycle of any service within IT. I didn't see this part, and I'm not sure if that functionality is already presented within Jira. I saw it in other products, however, in Jira I didn't find it. Maybe it comes at an extra cost, and this is in a paid version.

For how long have I used the solution?

I've used the solution for about four months or so.

What do I think about the stability of the solution?

I don't have experience with stability. My team would know more than I do.

What do I think about the scalability of the solution?

I'm planning to expand and change the license type, from the free one and to the professional one, in order to get more functionality and features. Our target is to do so in the coming year. Our plan is to increase usage. 

For the time being, we only have a limited number of people in the office using the solution. There are maybe only seven or eight of us on it right now. 

How are customer service and technical support?

We haven't needed to contact technical support yet. So far, everything has been very straightforward and we haven't needed help.

How was the initial setup?

The initial setup is not complex or difficult. It's straightforward. 

What about the implementation team?

I handled the initial setup myself, in-house. I did not need the help of a consultant or integrator.

What's my experience with pricing, setup cost, and licensing?

Right now, I am using the free version of the solution.

Which other solutions did I evaluate?

I'm comparing different desk and service management platforms. Jira is one of the top selected products, especially for the project management cycle. Jira was the best. I've tested many options, and many of them are well-known brands. 

What other advice do I have?

I'm just a customer.

I'd rate the solution at a nine out of ten. We've been happy with the product so far. 

I would recommend the solution to other users and organizations. 

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
IT Manager at Razi Insurance
Real User
The simple user interface helps non-English speaking customers use the software and it is highly customizable
Pros and Cons
  • "One of the main advantages of JIRA is that it can be customized for our solutions. I live in Iran and we translated some parts of it into Persian and customized it with extra features. We hid other features to customize it right to the point. We provide this solution for our customers."
  • "An improvement they could add is a better management dashboard. We only use the dashboard for the administration mode. We have a dashboard that reports the state of bugs or requirements. However, customers can only view requests that they made. We are not able to share a dashboard with our manager level customers to show them all of the requests in a quick dashboard."

What is our primary use case?

One of the main advantages of JIRA is that it can be customized for our solutions. I live in Iran and we translated some parts of it into Persian and customized it with extra features. We hid other features to customize it right to the point. We provide this solution for our customers.

It helps us shape it for our project management workflow. We are a software development team, a software company. Internally, we also use Microsoft Team Foundation, or TFS, for our development team, while we use JIRA Service Desk for our contact points. We use JIRA for the CRM and Microsoft Team Foundation for internal use.

How has it helped my organization?

We designed a single page on JIRA and classified it into three parts. One part reports software bugs, another part to report requirements about software development, and the last part for other requirements or needs. The customer can follow the links that we share. The system also sets permissions for our customers. I think we shared the agent mode. JIRA has two modes, one for administration and one for customers. We shared the customer mode.

Usually, our customers need two permissions, depending on their hierarchy. One level is the manager and the other is for a regular customer. We share it with our customer at two levels. The manager sees all of the requests that are sent from the organization. The regular user-level allows one to view only their own request.

What is most valuable?

It is simple to use. It is clear for our customer, who usually don't know English very well. The simple user interface helps them use the software.

What needs improvement?

An improvement they could add is a better management dashboard. We only use the dashboard for the administration mode. We have a dashboard that reports the state of bugs or requirements. However, customers can only view requests that they made. We are not able to share a dashboard with our manager level customers to show them all of the requests in a quick dashboard.

For Service Desk, I think the product now is very good and complete. Only the management dashboard for customers is a feature we would like to see in a future release. Maybe it is available already and we just can't find it.

For how long have I used the solution?

We've been using JIRA Service Desk for two years.

What do I think about the stability of the solution?

JIRA has very good stability. We haven't had any problems with it.

What do I think about the scalability of the solution?

We use JIRA in parallel with TFS. We connect them with a JIRA provided API. We use this API to connect with other products. Sometimes we must program for it to download some plugins and add to JIRA, for example. We can connect JIRA with other products this way.

How was the initial setup?

One of our technicians did the setup. I am the manager of a technical support team and I delegated this part of the project to one of my technicians. I think he ran a Windows server for the deployment. He installed JIRA on it and configured it. He searched how to install JIRA on a Microsoft Windows server and read the manual. I think we had no problem with the deployment process. He set it up, but I didn't hear about any problem with it.

What's my experience with pricing, setup cost, and licensing?

Actually in Iran we don't have copyright or intellectual property, so we can use JIRA for free.

It's uncomfortable, but because we don't have any laws about copyright, we must do it. We also do this with other products, like Microsoft's for example. We usually get them free. We have no problem using the full feature set free.

Which other solutions did I evaluate?

I searched about the top CRM in the world and compared features. Eventually, we selected JIRA.

What other advice do I have?

I would rate this as nine out of ten. If they add a dashboard for management customers, it would be a ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Khalid-Mehmood - PeerSpot reviewer
Program Architect - Service Quality at Afiniti.com
Real User
Workflow design is very simple; it's easy to develop any process or build any software with it
Pros and Cons
  • "Developing processes is easy and user-friendly."
  • "Currently lacks an asset management module that can affect deployment."

What is our primary use case?

We use JIRA Service for our help desk, our procurement processes, and for our financial approvals. We also use it for our technical team collaboration with lines. I'm a program architect.

What is most valuable?

I think it's very easy to develop any process inside Jira Service Management, you can build any software with it. It's simple to use and user-friendly. It's based on a technical system, but you can move any process into JIRA Service Manager very easily. Its workflow design is very simple and that's why people prefer this product. I think it's currently the best solution on the market.

What needs improvement?

Service Management currently lacks an asset management module that can make deployment more difficult. We recently had to purchase SolarWinds Asset Management to cover that aspect.

For how long have I used the solution?

I've been using this solution for 10 years. 

What do I think about the stability of the solution?

The solution is stable. 

What do I think about the scalability of the solution?

We have around 700 users so the solution is scalable.

How are customer service and support?

The customer support could be improved. 

How was the initial setup?

We used two or three of our developers for the initial setup and they also manage the server. It's not a large team.

What's my experience with pricing, setup cost, and licensing?

Licensing costs are on the expensive side. 

What other advice do I have?

The solution is suitable for mid-sized or enterprise companies and I rate it 10 out of 10. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free JIRA Service Management Report and get advice and tips from experienced pros sharing their opinions.
Updated: February 2025
Buyer's Guide
Download our free JIRA Service Management Report and get advice and tips from experienced pros sharing their opinions.