Basically, I am creating JIRA tickets, querying JIRA tickets, updating JIRA tickets, creating views for all the JIRA data.
Jira Service Management
AtlassianExternal reviews
933 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Team Leader Web Analyst
What do you like best about the product?
Ease of use, flexibility, stability,
What do you dislike about the product?
Nothing to add, everything has been working very well for years
What problems is the product solving and how is that benefiting you?
Uniformity of requests - everything is in one place.
search for requests very easy
linking of requests very practical
assignment of requests
archive
search for requests very easy
linking of requests very practical
assignment of requests
archive
Most used ticketing system in industry
What do you like best about the product?
Jira service managenent tool is used for ticket and tracking purpose. We can track all the tickets at one place
What do you dislike about the product?
The responsive time whole loading the page is high compared to other tools in the market.
What problems is the product solving and how is that benefiting you?
Jira service management tool workflows are configurable and tracking will be very easy.
super nice
What do you like best about the product?
the ticket management system and the tracking is nice
What do you dislike about the product?
super there are no issues so far i am happy
What problems is the product solving and how is that benefiting you?
It ticketing system
Innovative solution transforms data management with powerful query capabilities
What is our primary use case?
What is most valuable?
The query language and the ability to create views of the data are very useful. I can organize JIRA and set up tickets related to the projects I'm working on. It simplifies and accelerates my ability to manage tickets assigned to me or those I'm working with.
The dashboards are a good feature. The ability to actually edit dashboards is good. I can add modules into the dashboard to build out a sort of API, which is good. These capabilities are positive. Navigating around it is okay. A good example would be Visual Studio, which has an integration with Git.
What needs improvement?
I am not familiar if there's an integration with Visual Studio from Jira.
For how long have I used the solution?
I have been working with the company since 2022, so for just over two years.
What do I think about the stability of the solution?
There have been no problems at all. It has been a stable solution.
What's my experience with pricing, setup cost, and licensing?
The price is actually reasonable.
What other advice do I have?
Educate yourself on the capabilities of Jira to make the best use of the available technology. I would rate it nine out of ten.
Creates stories and tasks are easier with user-friendly tools
What is our primary use case?
For every project planning, we divide each project into different epics based on the milestones. Then for every epic, we create stories and tasks to complete within a two-week sprint cycle. After the two weeks, we have a review session with the clients to showcase our progress. That's how we are doing it.
What is most valuable?
The tool is scalable. It is not mainly about administrative efforts, however, as a working user, it is easier to create multiple stories and epics. For every task we are working on, the project manager can see the status once we update the stories mentioned. It helps overall project management to understand what the progress is and if there are any blockers.
What needs improvement?
One thing I would suggest is that before we create an epic, we mention the required stories in its description. Then AI could directly create those stories instead of doing it manually inside the table, so that integration can occur.
For how long have I used the solution?
I have been using it for more than six years.
What do I think about the stability of the solution?
Instability happens sometimes - although not frequently.
What do I think about the scalability of the solution?
The tool is scalable. As a user, it is easier for me to create multiple stories and epics, which aids in scalability.
How was the initial setup?
The company would have a new project assigned to it, and the team can work on it. The only effort required is during project planning. We need to organize the stories and other details, however, instead of using Excel, we can use Jira board to prepare everything.
What's my experience with pricing, setup cost, and licensing?
I have not worked directly on the pricing.
Which other solutions did I evaluate?
What other advice do I have?
It's a good experience. I rate it ten out of ten.
Simplicity and ease of use enables seamless customer configurations
What is our primary use case?
As a user, I configure it with my customers. I use it for simplicity and ease of use.
What is most valuable?
Simplicity is a key aspect. It is not hard to use.
What needs improvement?
The interface could be made easier to use. While it is not the worst, there is still room for improvement.
For how long have I used the solution?
I have used the solution for three or four years, perhaps.
What do I think about the stability of the solution?
I have had no problems with stability. It is 100% stable.
What do I think about the scalability of the solution?
I was not using an administrator role, so I had no such experience with scalability issues.
How are customer service and support?
I have never contacted technical support from Atlassian.
How would you rate customer service and support?
Neutral
How was the initial setup?
I have had no such experience with initial setup.
What's my experience with pricing, setup cost, and licensing?
It was not my responsibility as I was only a client. I did not handle the installation or purchasing.
What other advice do I have?
I would rate it eight points out of ten.
From my perspective, it was just good enough. It could be useful when it suggests what you can do for us. I am using it as an end customer, just through an interface. From my point of view, there is no specific need for automation, however, I am not an administrator. There were enough features for my needs.
Commonly used and manages sprints efficiently but needs more file management control
What is our primary use case?
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.
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.
showing 181 - 190