Feature tracking is a useful feature of JIRA Service Management. If there are multiple people in a team in an agile environment, it's very difficult to track whether something has gone to production or a feature has been worked on.
Jira Service Management
AtlassianExternal reviews
External reviews are not included in the AWS star rating for the product.
Very Good Product for project management
My experience with Jira Service Management during Automation
Jira : A complete tool for project management
Amazing Tool
All the information related to technical/non technical available in single platform
Overall this is nice tool
JSM review
A stable solution that can be used for feature tracking, planning, and execution
How has it helped my organization?
What is most valuable?
We use JIRA Service Management for tracking purposes, planning, and execution.
What needs improvement?
Field addition and removal features are not very intuitive in JIRA Service Management.
For how long have I used the solution?
I have been using JIRA Service Management for six to seven years.
What do I think about the stability of the solution?
We are satisfied with the solution’s stability.
I rate JIRA Service Management a nine or ten out of ten for stability.
What do I think about the scalability of the solution?
Around 15,000 to 20,000 users use the solution in our organization.
I rate JIRA Service Management a nine out of ten for scalability.
How was the initial setup?
The solution's initial setup is easy.
I rate JIRA Service Management a nine out of ten for the ease of its initial setup.
What was our ROI?
JIRA Service Management has helped our organization save time.
What other advice do I have?
JIRA Service Management is deployed on-cloud in our organization.
Overall, I rate JIRA Service Management a nine out of ten.
Easy to use, offers good stability and visibility for operational efficiency
What is our primary use case?
We use Jira Service Management (JSM) to manage tickets.
It enables us to track, monitor, and manage user requests from initiation to resolution. We use it for the end-to-end process. We can add comments, and close requests., so our primary use case for JSM is ticketing.
What is most valuable?
The interface is good and easy to use. We can track, monitor, and get all the details we need from the end-user's point of view for any service request.
What needs improvement?
The search function could be improved. We have to search a certain way. There is no generic search, it is more object-oriented search. The interface could also be more user-friendly.
So, the interface and search could be improved.
Additionally, I would like to see more accessibility. It would also be great if there was a Jira mobile app.
For how long have I used the solution?
We have been using JSM for more than two years. We have gained extensive experience with the tool during this time.
What do I think about the stability of the solution?
It is a stable solution. I would rate the stability a nine out of ten.
What do I think about the scalability of the solution?
It is in the cloud, so it is a scalable solution. I would rate the scalability an eight out of ten. It is very scalable.
Currently, it is being used by the entire organization, but for my team, we have around 10 to 20 people who use it regularly. In total, around 50 users have access to it.
How are customer service and support?
It is available, but we haven't had to use it much. We have been able to solve most of our issues on our own.
However, since it is a German-based product, there may be geographic issues with ticket routing.
They could improve it by providing support specific to the geographic location. They could also make 24/7 support available based on the availability of the support center.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We have used a few other Service Desk tools, but they are not at Jira's level.
Jira is a better tool to capture end-to-end details, which provides more visibility than the other tools.
How was the initial setup?
It's easy to deploy because it's a cloud-based model. There is no on-premises deployment required if you are using the SaaS model.
If you use the SaaS model, the maintenance is taken care of by the SaaS provider.
What's my experience with pricing, setup cost, and licensing?
It is one of the premium products on the market, but it is very costly, especially in the Indian market. Smaller organizations cannot afford it.
We pay monthly licensing costs. We only have to pay for the subscription model that we choose.
What other advice do I have?
Overall, I would rate the solution an eight out of ten. It is a good tool, but it is expensive. However, it does provide the information needed to make good decisions about operational development and performance. It provides good visibility, but it is also very expensive.