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.
Jira Service Management
AtlassianExternal reviews
External reviews are not included in the AWS star rating for the product.
JSM- great ITSM and ticketing tool
-Track tickets for almost all department viz. IT helpdesk, HR, Engineering, Purchase, Security etc.
-User friendly customer portal
-Add multiple users to a ticket as "Request participants"
-Availability of automation feature makes life of a jira admin much easier
-Unlimited custom fields options
-When typing up a summary, it gives the list of related old tickets where you might find the solution for your problem
-Easy to create escalation SLA's
-Ease of tickets escalations
-time tracking feature
-when you accidentally delete something, it's gone forever! (Deletion and recovery is not an option in Jira)
-limited upload size
-unavailability to copy Request types' configuration from one project to another
-Limited mobile funcationality
-Costly
-dark mode (it's really not so pleasant to work with - that's my personal opinion)
-inability to bulk close tickets
-non-intuitive
-inability to hide forms in the jira tickets/customer portal, if used.
-inability to migrate configurational changes from dev to prod.
It has really benefitted me to prioritize my tasks and see the progress of all my tickets in a single place.
Amazing Service tool for internal case management
Great service management solution
Effectively categorize, prioritize service request, problems, incidents.
ITSM solution best adapted to ITIL
Jira service management
All in one service & requests tracker for teams
Secondly, its also great for managing SOP's & incident management procedures.
A tool offering multi-functional capabilities to its users to cater to the needs of various departments of their businesses
What is our primary use case?
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.
Support and ticket management made easy
You can easily mix common support requests, with more long-term product update and bug issues. With clear labels separating the them.
All the user interface is clear, there really isn't much to it at all. If there were more formatting options, integration with other requests and a more concise to-do list, that would be great!
We can track such requests and make sure they are being promptly and appropriately dealt with.