Optimizing the IT and support departments to handle tickets without "going under" in the amount of work that they are doing by organizing the most important and urgent things first.
Director at a tech services company with 1-10 employees
Transparency of the system helps both internal and external persons involved
Pros and Cons
- "The automations will really help the company by delegating work the way your company operates."
- "It makes the IT department more transparent and helps the employees."
- "JIRA SD also helps for much better feedback on the work being done. All colleagues can see what is happening."
- "Transparency of the system helps both internal and external persons involved."
- "In general, JIRA has no relation to customers or financials. Therefore, marketplace add-ons are needed to make it work for customer-facing systems."
What is our primary use case?
How has it helped my organization?
JIRA SD releases pressure on the IT department and generates statistics. It also makes the department more transparent and helps the employees. JIRA SD also helps for much better feedback on the work being done. All colleagues can see what is happening. When the customer calls, everybody can see what is happening and the feedback via email when a ticket is modified makes sure the customer is informed and does not start calling. This releases pressure too.
What is most valuable?
Transparency of the system helps both internal and external persons involved. Statistics allow us to deploy resources where needed. It shows problem zones and where more capacity is needed or more training. JIRA SD also makes employees better as it helps them to feel more important when it comes to customer satisfaction.
What needs improvement?
In general, JIRA has no relation to customers or financials. Therefore, marketplace add-ons are needed to make it work for customer-facing systems.
Buyer's Guide
JIRA Service Management
January 2025
Learn what your peers think about JIRA Service Management. Get advice and tips from experienced pros sharing their opinions. Updated: January 2025.
832,138 professionals have used our research since 2012.
For how long have I used the solution?
More than five years.
What do I think about the stability of the solution?
No, it is running very stable, but only when you have a test system to try out things. As it is designed for developers, it is hard to convince developers to tamper with the production system.
What do I think about the scalability of the solution?
Yes, a plain vanilla installation will only last for less than 100 users. Handling more requires better hardware and configurations.
How are customer service and support?
Atlassian only has a very expensive enterprise support contract (>$100K) or email/JIRA-Ticket support. That support is included when you buy the license. After a year, you only pay for this support and not the license anymore. It is 50% of the new license costs and called a "renewal".
I would suggest to always buy licenses through an Atlassian partner, so you can also rely on their expertise. This way you have two support contacts and does not cost you anything more, such a partner will also come to the location, which Atlassian will never do (Atlassian only does email (JIRA-Ticket support). Phone calls to Atlassian will always be sales support advising to file a JIRA support ticket. Tech support is mostly concentrated in Australia, so there is always a time zone delay for the tickets you raise.
Which solution did I use previously and why did I switch?
We previously used CRM systems, like Vtiger CRM and SugarCRM. These are not intended for a development department.
How was the initial setup?
Setup (install) is straightforward, but needs tweaking when you are a heavy user.
Setup of the projects is made easier, but there is a lot more you can do beyond initial setup. The automations will really help the company by delegating work the way your company operates.
What about the implementation team?
We implemented with the aid of the vendor and external consultants.
What was our ROI?
It is hard to calculate costs you do not make.
It is also hard to calculate growing efficiency.
I can see that JIRA avoids chaos and makes the whole company work more efficient as all feature requests and internal/external requests are all visible in the JIRA tickets and the Confluence wiki system.
It made money the first year already.
What's my experience with pricing, setup cost, and licensing?
Costs are about $50 per user per year. JIRA is sold in user tiers of 25, 50, 100, 250, 500, 2000, 10,000, and unlimited users. It is bad when you have 51 users then the price is based on that 100 user tier. Users at 100 will be the most cost effective.
JIRA Service Desk has different pricing as it is based on agents. On average, the price is about $300 per agent.
Do not forget to calculate add-on costs. These cost a percentage of the JIRA purchasing costs and are based on the number of JIRA users.
Which other solutions did I evaluate?
Not really, as it was much better than Bugzilla which we used before.
What other advice do I have?
Buying a software solution is only a half part of the solution (or even less). You need to optimize usage of the software by hiring professionals who will help you to make the most of the software, especially in the beginning.
Repeat hiring of external consultancy every couple of years as knowledge fades out (people get different tasks to do). You should optimize your software infrastructure and re-evaluate it every three to four years to make optimal use of your infrastructure as the outside world changes very fast. Requirements also change.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Pre-Sales Solution Engineer at Amrut software pvt ltd
A tool offering multi-functional capabilities to its users to cater to the needs of various departments of their businesses
Pros and Cons
- "The most valuable feature of the solution is its SLA, which everybody wants when it comes to a service-based offering."
- "In-built chat is missing in JIRA Service Management."
What is our primary use case?
JIRA Service Management was used strictly for our client's IT services in my company. Nowadays, the tool caters to business needs, HR, and administrative purposes, including the payroll aspect of my company's clients. The application has taken a different turn by allowing for managing certain relevant business needs as well.
How has it helped my organization?
In recent scenarios, JIRA Service Management has helped my company's clients on the automation front, including onboarding or offboarding employees. The product has multiple use cases with multiple departments, one area that gets highly utilized. The tool also helps convert an incident into a change or problem and then trace and track activities with the tool, which is highly leveraged. Integration of JSM with JIRA software on change and problem management to drive the release, and looking at the release on the DevOps chart, are some use cases by businesses.
What is most valuable?
The most valuable feature of the solution is its SLA, which everybody wants when it comes to a service-based offering. The queues in JIRA Service Management play a vital role in allowing its users to define the issue types, further classify them into queues, and then carry on.
What needs improvement?
In-built chat is missing in JIRA Service Management. To compensate for the missing in-built chat, we have been trying to gain leverage with Slack or Microsoft Teams at the moment since it is important to me who stands between the customer and the agent. The aforementioned area needs improvement because it is a very vital area. Suppose one can get on to something in JIRA Service Management that allows for communication. In that case, it is easier to solve a problem rather than communicate with JIRA through comments which will go back and forth.
In short, an in-built chat option will be good for the solution.
For how long have I used the solution?
I have been using JIRA Service Management for over six years.
What do I think about the stability of the solution?
It is a stable solution. Stability-wise, I rate the solution an eight to nine on a scale of one to ten.
What do I think about the scalability of the solution?
Scalability-wise, I rate the solution an eight to nine on a scale of one to ten.
How are customer service and support?
I rate the technical support a nine out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I used to previously work with Bitbucket.
How was the initial setup?
I rate the initial setup phase of JIRA Service Management a six out of ten.
The solution is deployed majorly on the cloud.
The time taken to deploy JIRA Service Management depends on multiple factors. It can range from a week to a month, depending upon what kind of customization and plug-in integrations are required.
What's my experience with pricing, setup cost, and licensing?
JIRA Service Management's pricing is pretty decent compared to competitors. I rate the pricing an eight to nine on a scale of one to ten.
What other advice do I have?
To those planning to use it, I would say that if they have a larger customer base, which may cause them to incur some licensing costs, then that is the area where they should look at JSM as a candidate. If some want to automate their internal processes, which could be operational, business-centric, or technical operation, they can use JSM. People who can look at JSM as a candidate are those who have a little bit of asset requirement where they want to manage the instance and opt for the trace and track functionality to find out what exactly is happening and who is honing what in general.
Overall, I rate the solution a nine out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer:
Buyer's Guide
JIRA Service Management
January 2025
Learn what your peers think about JIRA Service Management. Get advice and tips from experienced pros sharing their opinions. Updated: January 2025.
832,138 professionals have used our research since 2012.
Vice President of Products at Incivus Inc.
Efficient workflow management for tracking and resolving queries but not very user-friendly interface
Pros and Cons
- "With Jira Service Desk, the simplicity of setting up a quick form and getting the service desk running quickly is very helpful."
- "Initially, as a completely new user, the interface was not very user-friendly, with many cluttered options."
What is our primary use case?
I use Jira Service Management for product development. Jira Service Desk is largely for handling customer queries and internal ticket management. It helps us with any IT-related requests and also allows customers to submit feedback for the product. So that's how we use Jira Service Management.
How has it helped my organization?
Jira Service Management provides workflow management, making it easy for us to track queries and provide solutions. It allows us to review historical data to see how our response time to queries has improved over time. This feedback loop helps us enhance our services and products based on customer input and Net Promoter Score (NPS) feedback.
What is most valuable?
Different projects benefit from various features. With Jira Service Desk, the simplicity of setting up a quick form and getting the service desk running quickly is very helpful.
On the Jira Software side, I find the idea management feature valuable. It allows us to maintain a backlog of ideas submitted by customers, employees, and product engineering teams. We can track where ideas originate, follow their development into the product, and engage with customers throughout the process, providing a powerful capability.
What needs improvement?
One area I see for improvement is the custom options for marking an idea as obsolete. Currently, there are options like "not started" or "not working," but in today's rapidly changing tech world, some ideas can become obsolete quickly. For example, technology may become obsolete or a product may no longer be able to cater to a certain idea due to business pivots or changes in the product strategy. However, there is no specific option to indicate why an idea is considered obsolete, whether it's due to technological changes, business model shifts, or other reasons. Capturing these business-driven changes is not easy within the current setup.
It would be beneficial to have a configurable drop-down where we can filter and categorize the reasons for obsolescence, including technical, standard cases, and, importantly, business reasons. If such an option already exists, it might not have been effectively communicated to customers, as I haven't come across it yet within the customer community.
It's essential to have clear ways to manage and track the obsolescence of ideas based on both technical and business considerations.
For how long have I used the solution?
I have been using Jira for more than six years. I currently use the latest version.
What do I think about the stability of the solution?
I would rate the stability a nine out of ten. Stability is pretty good; there's never a significant downtime. It's been great.
What do I think about the scalability of the solution?
It is highly scalable. I would rate the scalability a nine out of ten. We have 500+ end users using this solution. Almost all of our employees use this solution.
It's used every single day, heavily utilized for Jira Service Desk and Jira Software for product development. We use it to its maximum potential.
How are customer service and support?
While Jira has a decent community where you can find answers, technical support is fairly okay, mostly due to their strong community.
How would you rate customer service and support?
Neutral
How was the initial setup?
I would rate my experience with the initial setup a six out of ten, where one being difficult and ten being easy.
Initially, as a completely new user, the interface was not very user-friendly, with many cluttered options. However, once someone showed me how to use it, it became less challenging. But for new users starting with self-service abilities, it's not up to the mark.
What about the implementation team?
The deployment didn't take too long, maybe two or three weeks. It is a self-maintained solution.
What was our ROI?
We have seen an ROI. The standard way of operating with Jira has optimized time efficiency, which translates to cost efficiency. It allows us to resolve issues more efficiently, although the interface complexity might slightly impact overall efficiency.
What's my experience with pricing, setup cost, and licensing?
The price is not high. I would rate the pricing a seven out of ten, where one is low price, and ten is high price. It's competitively priced, considering other similar products in the market.
There are no additional costs. The license we have covered quite a few offerings, like Jira's Confluence page, so that's pretty good.
What other advice do I have?
If you have a large organization with complex processes and need to scale up, Jira Service Management is an excellent platform for service and development management. However, if you're looking to optimize operations, improve services through data insights, and have a large organization, I would recommend considering ServiceNow as well.
Overall, I would rate the solution a seven out of ten. It's a solid solution with some room for improvement, but overall, it's a valuable product for our organization.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Manager at GMX
The basics are solid, but I'd like to see improvements in advanced queries, UI performance, and support for collaborative editing
Pros and Cons
- "Jira gets the basics right in terms of the product backlog and a scrum board teams can use to manage sprint backlogs."
- "The queries are weak and lack advanced functionality. You can do rudimentary queries, but you can't aggregate. You can't filter for a lot of things that would be useful, so you need to use plugins to write writing advanced queries. I run into problems when working with different organizations because they always have restrictions on what kind of plugins they allow."
What is our primary use case?
Currently, I'm not working with an organization that is using Jira, but my previous clients have used it. The last client had 15,000 licensed users, of which about 7,000 or 8,000 were active. I'm not sure how many of those were using it on a daily basis, but I'm guessing it was about a third.
What is most valuable?
Jira gets the basics right in terms of the Product Backlog and a Scrum Board that Scrum Teams can use to manage Sprint Backlogs.
What needs improvement?
The queries are weak and lack advanced functionality. You can do rudimentary queries, but you can't aggregate. You can't filter a lot of things that would be useful, so you need to use plugins to write writing advanced queries. I run into problems when working with different organizations because they always have restrictions on what kind of plugins they allow.
For how long have I used the solution?
I have been using Jira for around 14 years, and Jira Service Management specifically for about half a year.
What do I think about the stability of the solution?
Jira is fairly stable.
What do I think about the scalability of the solution?
The user interface becomes sluggish when there are many items in the database, especially large Product Backlogs. I've had page-load times of more than 30 seconds on modern clients. That's just unacceptable. A lot of things are processed through the user interface when it might be smarter to process them through the backend. It tends to be quite slow because it's a JavaScript user interface with a lot of dynamic processing, and a lot of it is run sequentially, single-threaded. For this reason, Jira especially benefits from modern browsers with a fast JavaScript engine, such as Chrome or Edge, and of CPUs specifically optimized for dynamic website processing, such as the Apple M series.
How are customer service and support?
Atlassian support is excellent. I contacted support once directly because I was using a free license on a pet project, and I had to log in again, or they would deactivate my account. I logged in to prevent that from happening, but it still was deactivated, so I contacted them. They took care of it.
Most of my work is with internal IT departments who administer Jira as an on-premise installation. They provide internal support to users, and my invoke Atlassian as a second level on their behalf. The on-premise installations often have lousy support. They tend to be over-bureaucratized IT departments that don't care much about user needs. It's just the kind of environment that brings that out.
How was the initial setup?
I rate Jira 10 out of 10 for ease of setup. The setup is handled centrally by an administrator. I also use the Atlassian software as a service, so the setup is negligible. It's ready to go out of the box, unless by all means you want to host it yourself.
What was our ROI?
We never calculated the return on investment. Jira is useful when your teams are virtual and distributed across several sites or when there are many items, especially when they need to be tracked for compliance reasons. Software like this is always useful in those cases. It may be less valuable if everyone is in the same place and there are only few larger items to handle, in an environment that gives more leeway in terms of compliance.
What's my experience with pricing, setup cost, and licensing?
The license is based on the number of users. Jira gets costly when scaling up to high numbers of users. At a certain point, it might be more cost-effective to create a custom solution or use something else.
What other advice do I have?
I rate Jira Service Management seven out of 10. The basics are good, but I'd like to see improvements in user-interface performance and scalability. Querying functionality is also limited. It would be nice if Jira allowed more advanced queries. The user interface doesn't lend itself to working concurrently, with multiple users having a conversation and using the system concurrently. Those are areas for improvement. I would rate it a 10 if it had those. But it does not.
Before deploying Jira, I recommend researching the product to see if it meets your needs. Jira fits a very wide range of needs. But there are a few situations where it is not optimal, or needs to be used in an augmented way. For example, it shouldn't be used to support Scrum events directly, because the user interface doesn't lend itself to working concurrently. You need to update frequently to see changes made by others, and actions are generally sequential. If I need a solution, e.g., for a Daily Scrum, I'd much rather use something like Mural or Miro, and then have it interface with Jira. While Jira can ultimately still be used in these scenarios, as the backend, it benefits from some kind of digital whiteboard on the UI end that allows people to work concurrently with it.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
IT Manager at MTF Industriel
Reliable, easy to use, and easy to manage
Pros and Cons
- "The platform is easy to use."
- "The interface could always be updated and improved."
What is our primary use case?
I use the IT help desk Level One to manage tickets.
In Jira, when a client creates a ticket, I read the ticket, then I respond to the ticket. After the problem is solved, I assign the ticket to me.
If the problem is not solved or harder than Level One, I escalate it to Level Two so that level two can handle the problem.
In my role, I get tickets from people, then try to solve them. If I solve it, I assign it to me. If not, I escalate it to someone with better knowledge than me. That's it, my role. I handle some phone calls as well.
What is most valuable?
The platform is easy to use. We can manage it very easily.
You can understand easily. It is not complicated.
The initial setup is easy.
It's a reliable product.
What needs improvement?
I don't have much experience to give a solution for this. I'm not sure what could be improved.
The interface could always be updated and improved.
For how long have I used the solution?
I've only used the solution for one month.
What do I think about the stability of the solution?
The solution is reliable and stable. The performance is good. There are no bugs or glitches. It doesn't crash or freeze.
What do I think about the scalability of the solution?
I'm not sure if you can scale the solution. It's not an aspect I've studied.
80% of our company uses it. However, it's not that big of an organization. In our department, there are five of us using the product.
How are customer service and support?
Technical support is so-so. Some of them are good, some bad. It depends on the people. Some people are respectable, some don't really respect others.
Which solution did I use previously and why did I switch?
I've worked with Spiceworks in the past.
How was the initial setup?
It's easy to implement. It's not complex or difficult.
The time it takes to deploy varies. It depends on the complexity of the problem. Some problem takes five to ten minutes, and some problems take an hour. It depends on the problem.
We have admins that can maintain the solution. I tend to manage it myself.
What's my experience with pricing, setup cost, and licensing?
I'm not sure how much the solution costs.
What other advice do I have?
I'm a normal user.
I haven't focused a lot on updates. I'm not sure which version we're on.
I'd recommend the solution. It's easy to use and the fastest way to handle a ticketing system.
I'd rate the product eight out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Director at a financial services firm with 1,001-5,000 employees
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.
Founder at Solvitech
Reasonable price and quick compared to other solutions, with great technical support
Pros and Cons
- "Compared to other solutions, Jira Service Management is really reasonable regarding price and speed."
- "In the Turkish market, the biggest problem is that they are looking for a server type of solution, but when it comes to Jira Service Management, Atlassian is a remote type of license. There are just two different options, data center and cloud."
What is our primary use case?
Most of the use cases were finding solutions to customer problems and SLA cases. We worked with customers on some cases like call centers and with some companies who would like to solve their customer's problems. We also worked with the banking industry and insurance industry.
I have worked at OBSS, which is one of the biggest software companies in Turkey. They were also one of the Atlassian Solution Partners in Turkey. I recently left that company.
What is most valuable?
Compared to other solutions, Jira Service Management is really reasonable regarding price and speed. Technical support from the Atlassian agents is great.
What needs improvement?
In the Turkish market, the biggest problem is that they are looking for a server type of solution, but when it comes to Jira Service Management, Atlassian is a remote type of license. There are just two different options, data center and cloud.
When I was working at that company, we started to work with Central Bank of Turkey. We also worked with the defense industry. The biggest complaint was about data privacy. If Atlassian opened a data center in Turkey, that would be a very good solution for these kinds of companies.
Some plugins could be implemented into Jira Service Management, like our plugin. We had our own plugin calculated each status and how much time the company spent in each status.
For how long have I used the solution?
I have used Jira in the past 12 months. We were using the server type of license. I don't remember the exact version we used, but I have also used the cloud version of Jira Service Management, which was called Jira Service Desk in the past. I used it for more than three years.
What do I think about the stability of the solution?
The solution is stable.
There were three or four people working on maintenance, but their work was not only in Atlassian. They were working as system engineers. This is one of the responsibilities of maintaining Atlassian products and services.
What do I think about the scalability of the solution?
The solution is scalable. The data center's most popular feature is being scalable. The cloud is very fast, and setting it up is very easy.
Our company had around 500 people, but after I left the company, it was around 700 or 800 people.
How are customer service and support?
Technical support is good.
When we created a ticket on Atlassian, they were also working SLA services, L1, L2, L3, and L4. When we created a ticket, we were getting very good service from an agent. In some cases, we had talks with our channel manager, especially about the cost of licenses.
Which solution did I use previously and why did I switch?
We previously used Confluence, Puppet, Bamboo, and HipChat, and then it was sold to Slack. We used Fisheye and Crucible as well. We were using most of the solutions regarding Atlassian. In my daily life, I have also used Trello.
How was the initial setup?
I worked mostly as a business developer, but when I received feedback from our deployment staff, they said it was not difficult to deploy the solution. Cloud is very easy to use. You just can start to work with it.
What's my experience with pricing, setup cost, and licensing?
The license we use is on a yearly basis. As a Solution Partner, we were using the free one and were using the free plugins. We were also giving our own plugins to the Atlassian Solution Partners for free. We don't pay anything to Atlassian.
What other advice do I have?
I would rate this solution 9 out of 10.
Sometimes the beginning of the implementation and working with custom-built workflows was a little bit difficult for regular companies. At this step, I strongly advise that they work with an Atlassian Solution Partner.
Specific industries need specific solutions. Atlassian partners have a lot of experience, maybe in that specific country and in that specific company field.
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.
Agile Couch at Fusoft
An excellent solution for tracking customer service issues and tracking technical support issues
Pros and Cons
- "This is the most complete and versatile enterprise task management product and issue tracker."
- "Integration possibilities with other products that are not Atlassian would be helpful. Support should also provide separate installation guides for each product even though they are easy to install."
What is our primary use case?
JIRA Service Desk is used as a support solution with the support team to manage support service delivery to customers. I coached a big banking company using JIRA Service Desk to record customer incidents that require support. With the product, we have two different layers of incident management. Level one is for the call center and level two is for the agents who repair or try to resolve the incident using a software team.
If their team can't resolve the problem, we create particular bug issues in JIRA software, and the development team creates a plan to correct the issue and confirms the experience in order to provide a resolution. The issue is returned back to layer two, and layer two discusses the problem with layer one. After that, layer one speaks to the customer and explains the status of the problem.
How has it helped my organization?
It helps us to provide better customer service.
What is most valuable?
The best part of the application for me is the ability to manage the issues. Within the different layers, you can set priorities, define task management, assign tasks to the software team or to different groups or functions to help manage solutions in JIRA. I use different features in JIRA Service Desk for the software team. It is a broad solution that affects different layers of the organization.
Because the software team and development team can use the solution to manage and track projects more efficiently and work together as a team, they find and resolve problems better.
What needs improvement?
I think that JIRA Service Desk is a very good product and that it is full of features that work well to manage tasks. It has the flexibility to handle many different activities and it is very good at this. Especially in the latest version, it has some new features and capabilities that were added so that it is even better.
The one thing I would like to see is better capabilities to integrate with products other than parts of the Atlassian system. For example, if there is a Microsoft product that is better for another team the integration may be difficult or impossible.
Any one business process software can't do everything a system needs. For example, I have experience with JIRA and TFS (Team Foundation Server). TFS is a very good application and a good solution for software development teams. It's not the perfect solution for all parts of an organization and maybe does not fit an organization's needs well. In some cases, it may be better. It depends on the use. If you want a broad solution for your company, for task management, or issue tracking, TFS is not a good solution. For software development, TFS is very, very good and may be just what you need.
After using the product and knowing the benefits of TFS, I thought that combining the systems would be the best solution: the combined system could help the company to decrease the time it took to process software issues. I think JIRA Service Desk does not have features that are as good for tracking fix times or bottlenecks in the process. You can use different plug-ins for JIRA Service Desk to add some functionality, but these plug-ins are very expensive. It would be nice if JIRA Service Desk added in some of these features for this type of support.
But about the plugins, I found one plug-in — its name is Actionable Metric I think — and it is $3000. That is very expensive for users in Iran. For most customers, I would not be able to propose this solution because it's very expensive. But it is also very important to some of the projects I consult with. Because of that, it eliminates JIRA Service Desk from consideration, because we can't integrate them into the system.
For how long have I used the solution?
I have been using JIRA Service Desk for four years
What do I think about the stability of the solution?
The product seems very stable. We have never had a problem.
What do I think about the scalability of the solution?
I think the product is very scalable as long as the hardware can handle the usage.
We have never had a problem. Two years ago, I had a launch of Service Desk in a bank in Iran and we had 8,000 issues to track for the core banking system.
This launch was very, very good because we used an IT framework in this company and returned used a post egress system for response to bank customers or bank users. We could use Jira software for the response to this incident and resolve that.
We had 8,000 issues two years ago, and the company continues to use this product and I am sure that they have been able to scale and track more.
How are customer service and technical support?
The Atlassian technical support is actually very good and responsive.
Which solution did I use previously and why did I switch?
I worked in a different company and when I was there they were using a different solution. It was an airplane company in Iran. For part of my job, I was tasked with finding the best solution for managing tasks in different layers of the organization — different tasks for different departments. For example, I wanted them to record requirements for cost and team level or management level. Unfortunately, with the product they were using, I could not find these solutions for task management. As this was critical, I needed to do some research into other task management solutions. After a search I found some reviews on ITCentralStation.com, I found from the reading that the Atlassian system would be better to serve our needs because of the features. I looked at other solutions and reviews but I finally chose the JIRA system.
This is the best application for me because it supported different solutions and could be one big solution for different layer of the organization using JIRA Service Desk, JIRA software, or JIRA Core.
How was the initial setup?
While I think the installation and deployment were very simple for me, the company should have different ways to find solutions independent of technical support and they need a better installation guide for installing different applications. My team and I tried to do an installation on the last server for a new client in a different environment than we usually use. We installed different portals for addressing that and I have had experience installing two or three of the top DevOps tools. This was very easy by comparison.
There have occasionally been some problems, but it is usually very good and very simple.
What about the implementation team?
I am an Agile development coach and systems consultant and our team does our installations ourselves.
What other advice do I have?
I think I had the opportunity to learn a few things by working with JIRA Service Desk. It has been a good solution and supports good practices, but it is not everything every company needs. I can't find a better single solution for a better approach to tracking and better customer satisfaction. I have a better picture of customer needs and gradation.
I have more experience in JIRA software because I worked with it in many different companies now. Some years ago I was a Java Software developer and had a lot of experience with Scrum and agile development and we used JIRA software. I think I can speak better about JIRA software because I was a software developer.
On a scale from one to ten, where one is the worst and ten is the best, I would rate JIRA Service Desk as a ten. For my experience, it is the best product on the market for use in enterprise installations.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free JIRA Service Management Report and get advice and tips from experienced pros
sharing their opinions.
Updated: January 2025
Popular Comparisons
ServiceNow
BMC Helix ITSM
IFS Cloud Platform
ManageEngine ServiceDesk Plus
Freshservice
Ivanti Neurons for ITSM
SymphonyAI IT Service Management
Clarity SM
OpenText Service Management Automation X (SMAX)
Buyer's Guide
Download our free JIRA Service Management Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Should I migrate from TopDesk to JIRA?
- HIPAA Compliance with JIRA
- What are the differences in purchase and maintenance costs for ServiceNow and JIRA Service Desk?
- What are JIRA Service Management's automation capabilities?
- CA Service Desk vs IBM Maximo
- What is your recommended IT Service Management (ITSM) tool in 2022?
- HIPAA Compliance with JIRA
- What is the best lightweight ticketing system with superior communication options for an educational organization?
- Do you think, it's better for a company to evolve IT tool consolidation, or change tools by revolt?
- When evaluating IT Service Management, what aspect do you think is the most important to look for?