I am primarily using Jira Service Management for sprint management, estimations, planning, pre-planning, and conducting all the sprint ceremonies with user stories and estimations.
Jira Service Management
AtlassianExternal reviews
937 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Commonly used and manages sprints efficiently but needs more file management control
What is our primary use case?
How has it helped my organization?
It's commonly used, so we don't need to teach anyone. Any new member that joins knows Jira Service Management.
What is most valuable?
Everyone knows how to use it, so there's no need to teach new members. It's as widely recognized as word processors.
What needs improvement?
Jira Service Management could improve by offering more control similar to Monday.com, such as easier automations, file addition, and sharing with different people.
For how long have I used the solution?
I used it a lot before stopping three months ago.
What do I think about the stability of the solution?
We never faced any latency or stability issues. My team had never more than six or seven people, and it was stable for our needs.
How are customer service and support?
I had to use support management tasks regarding the API. They didn't help with my issue because it was something that was not supported.
How would you rate customer service and support?
Negative
Which solution did I use previously and why did I switch?
I used NetSuite and considered monday.com to be more beneficial.
What was our ROI?
It returned value, but I'm not sure if it completely covered the investment. It's useful.
What's my experience with pricing, setup cost, and licensing?
Jira Service Management is expensive and not worth the money compared to monday.com.
Which other solutions did I evaluate?
I used NetSuite and evaluated monday.com, which has more control and features I find beneficial.
What other advice do I have?
I rate Jira Service Management a six out of ten. I used monday.com due to its ability to provide more control, automations, and better file management.
A Extradinoary Ticketing Tool
What do you like best about the product?
Jira Helps It organization with N number of features.Not A high recommonded space , we can implement many automation things, And now a days it help ful to all empolyee to see work details and tickets and get approval easier.
Ver good backend support for the jira users.
A custom dashboards for teams in organization and gives good alerting in slack integration.It helps in use day to day activities in Soc related .We use it in day to day. It is built in cloud environment.
Ver good backend support for the jira users.
A custom dashboards for teams in organization and gives good alerting in slack integration.It helps in use day to day activities in Soc related .We use it in day to day. It is built in cloud environment.
What do you dislike about the product?
No disadvantes as per now i use liked a lot
What problems is the product solving and how is that benefiting you?
It solved the ticket helping for IT team to identify the type of alert .
Simplifies tracking issues and updates effectively with useful task assignment
What is our primary use case?
My primary use case for JIRA is to track tickets while working in an agile mode. I use it during each sprint to keep track of all my team members. All the data is there, which makes it easy to analyze at the end of the year and evaluate what we have accomplished.
What is most valuable?
Using JIRA simplifies tracking issues and updates. It allows me to assign tasks easily to colleagues. This way, I don't need to set up meetings for every issue since there is a discussion space in JIRA. It is beneficial if someone is on vacation sincew others can follow up on the tickets.
What needs improvement?
An AI feature that enables automation and alerts for users can be an improvement. For example, users should receive weekly reports.
For how long have I used the solution?
I have been using JIRA for the one year.
What do I think about the stability of the solution?
I have not checked any latency or stability issues, so I cannot provide a definitive answer.
What about the implementation team?
The implementation team is different from my team since we are only users of JIRA. The updates and patching are handled by another team.
Which other solutions did I evaluate?
Other teams in my company are using MongoDB and SQL, however, I am not using them in my project.
What other advice do I have?
We are the users of JIRA and only have limited access. I do not have any additional advice or ratings.
Efficiently track and document projects with seamless tool integration
What is our primary use case?
We are a management warehouse that provides services to different customers in different sectors. Primarily, we serve the banking sector and the military sector. We manage all the software delivery projects through tools such as JIRA Service Management or TFS.
What is most valuable?
Confluence is a great tool for documentation and tracking. Additionally, Bitbucket is essential for controlling the source code. JIRA itself is valuable for managing tickets, user stories, and pipeline. The integration between different tools provided by Atlassian products is also significant.
What needs improvement?
The licensing model could be improved. There needs to be a different licensing model for large numbers of employees, as it remains one of the main barriers to using JIRA Service Management across our entire company.
For how long have I used the solution?
I have been using JIRA Service Management for more than 15 years.
What do I think about the stability of the solution?
JIRA Service Management is generally stable. I did not face any issues with its stability.
What do I think about the scalability of the solution?
The scalability is rated eight out of ten. It is quite scalable for our company environment.
How are customer service and support?
I have contacted Atlassian support maybe once or twice, and the support was good.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We are also using TFS for several projects. TFS is good, however, it lacks the ecosystem found in Atlassian products.
How was the initial setup?
The initial setup is not difficult. Since we are using the cloud version, there are no issues with the installation. On a scale from one to ten, it's rated as an eight for ease.
What's my experience with pricing, setup cost, and licensing?
While JIRA Service Management saves time, direct cost savings are challenging due to licensing fees. Currently, it costs around $150 to $200 per user, a significant expense, especially given the large number of employees.
Which other solutions did I evaluate?
We evaluated TFS before using JIRA Service Management. It is also good, however, we prefer the Atlassian ecosystem.
What other advice do I have?
I recommend JIRA Service Management and rate it eight out of ten.
Jira Service Management is the best
What do you like best about the product?
The interface is straightforward, making it simple for everyone to find what they need without getting lost.
What do you dislike about the product?
Setting up workflows and customizations can be time-consuming and sometimes confusing. sometimes i feel like it require a developer to do that
What problems is the product solving and how is that benefiting you?
It was hard to keep track of service requests, now Jira organizes everything, so we can respond quickly and nothing slips through the cracks.
Jira Service and project management
What do you like best about the product?
Streamlined project management as well as queue management
What do you dislike about the product?
Notification settings on Jira when new tickets are created. Being browser based you manually have to refresh in order to see any changes to the lobby
What problems is the product solving and how is that benefiting you?
Service desk and ITSM split to streamline ticket queries appropriate for support teams as they have been configured
Enables customized real-time communication but requires UI improvements
What is our primary use case?
I'm currently using JIRA Service Management for project management, specifically for communication with different tech tools and providing services for our product. It is mainly used within the research and development department, governed by product managers and service managers in operations.
How has it helped my organization?
It provides real-time updates to all the stakeholders, which is the best aspect of the service. It offers the opportunity to create customized communication and service tracking, allowing for more precise real-time changes.
What is most valuable?
JIRA Service Management provides real-time updates to all the stakeholders. It also offers the opportunity to create customized communication and track services, enabling more precise real-time changes and a customized version.
What needs improvement?
The platform should be more user-friendly. JIRA's user interface needs training to understand and utilize. There is a need to limit the information in one window to avoid overwhelming users with unnecessary data.
For how long have I used the solution?
I've been working with JIRA Service Management for about two to three months.
What do I think about the stability of the solution?
I would rate the stability a seven. There should be more governance for permissions and more options for customized access without frequently involving the admin.
What do I think about the scalability of the solution?
I would rate scalability as eight or nine. It supports introducing new features or levels efficiently across our global locations, helping everyone stay informed.
How are customer service and support?
I communicate with technical support monthly, but they provide the same information available online. I would rate them a five.
How would you rate customer service and support?
Neutral
How was the initial setup?
The initial setup is complex. It's rated at a seven. Too much information is presented at once, leaving room for simplifying and customizing views.
What about the implementation team?
I primarily handled the implementation, utilizing available videos and documentation for setup and understanding.
What's my experience with pricing, setup cost, and licensing?
Pricing seems slightly expensive compared to others but offers solutions on the AWS level, which could justify the cost. I would rate it a seven on the expensive side.
What other advice do I have?
New users should consider tools that are not only feature-rich but also easy to use. Many providers offer robust features, so the ease of use should be a deciding factor. I would rate JIRA Service Management a seven overall.
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?
Amazon Web Services (AWS)
Offers free features but limited support and integrations
What is our primary use case?
We use it primarily for test case management and raising bugs. It is a centralized tool that we use to track test cases, integrate with automation, and manage bug fixing.
What is most valuable?
The most valuable feature of Jira is that it is free of cost, which is a significant advantage. Bug raising is easy, and integration with other tools is straightforward.
The centralized feature allows us to track test cases and integrate with automation and bug fixing.
What needs improvement?
We faced challenges with integration for different frameworks like TestComplete. The support we received was not fully provided at that time. The free version of Jira does not have many features. AI features for integration, test case scheduling, and requirement management could be enhanced.
For how long have I used the solution?
We have been using it for two to three years.
What do I think about the scalability of the solution?
In the initial period, only 25 team members were using it, and it worked for us without requiring changes.
How are customer service and support?
The support provided at that time was not fully sufficient.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We used Team Foundation Server, now known as DevOps, after we stopped using Jira due to the availability of licenses and the needs of our clients.
What's my experience with pricing, setup cost, and licensing?
We used Jira's free version for some time, and we used it as an offline service without communicating with the Jira team regarding the license.
What other advice do I have?
I'd rate the solution six out of ten.
Not my favorite Csm app, but solid.
What do you like best about the product?
Easy to navigate. Sharing across multiple teams is crucial in roles like mine, and I'm able to manage all of my tasks with ease.
What do you dislike about the product?
There is a learning curve. I feel better onboarding and training can improve the process
What problems is the product solving and how is that benefiting you?
It keeps my service level tickets seamlessly linked to my projects and dependencies. Improves communication cross functional
VP of Marketing
What do you like best about the product?
Easy to setup, easy to use to route requests for each functional group within Marketing
What do you dislike about the product?
Setting up the right framework for Jira initiatives, objectives, epics and task are aligned for Dev & IT construct as opposed to marketing teams.
What problems is the product solving and how is that benefiting you?
The ability to manage Marketing. request for the entire organization.
showing 191 - 200