JIRA Service Management Reviews

Pros

To accommodate the fact that various people have different ways of doing things, this user interface may be easily altered to fit individual needs. Jira makes it simple and quick to design and implement unique workflows and rules. One way to break down large projects into manageable chunks is to keep everyone in the loop on how things are shaping up.

Cons

Jira's flexibility allows for personalization, but more in-depth modifications may call for specialized skillsets.Performance difficulties: Some users may have performance issues, especially when working with larger projects or those that include complicated procedures.

Pros

It is a slightly different tool from the so-called general ITSM system (or service). Operation and maintenance (though not limited to) tend to be individualized. Still, JIRA caters to tasks and support on a "role" basis, so sharing knowledge using OJT is possible, depending on ingenuity.

Cons

It may be a problem due to the multifunction, but I think the problem is that the screen is a bit hard to see. (The problem may be solved by changing the layout of frequently used functions, but I haven't used it much yet, so I think it will be a problem that will be solved as I use it).

Alternatives Considered

ManageEngine ServiceDesk Plus

Reasons for Choosing JIRA Service Management

Because we can search by tag, we can quickly find problems and solutions, success stories and reference examples. Since the SLA can be configured according to individual design, the achievement status can be confirmed in a report, and the current progress and what needs to be done can be shared immediately. Full-text search is possible with indexing, so this system has a sense of security, even if you think you missed it.

Switched From

ServiceNow

Reasons for Switching to JIRA Service Management

Functionality that manages queries centrally. Improved working conditions enhance visualization and efficiency. Queries, support and information distribution are centralized, so there is no waste in work, and it is simple and clear what to do next so that I can do my job.

Pros

Service Management is very easy to get going "out of the box" for small organizations. We stood this up apart from our enterprise's main service management tool because we had special needs for our intake forms and this allowed us to do the customization needed without going through rigorous development through the enterprise level tool.

Cons

Form design for your main portal can sometimes be wonky, as navigating through the options takes a bit of getting used to and aren't the most intuitive at first. Workflows are also very simple and complex decision-making based on external data is not readily available.

Alternatives Considered

ServiceNow

Reasons for Switching to JIRA Service Management

Service Management ultimately was chosen because it integrated perfectly with our Jira instance and allows for seamless story/epic creation from internal customer requests, porting the information over was made very easy by this fact and the workflows you can create between the two are very useful.

Pros

Highly customisable service desk portal, from the fields to the UI. We can set up a new portal in minutes for every new project and easily tie the tickets to our internal Jira Software projects keeping internal and external discussions separate.

Cons

SLA management should be made easier as well as the reporting options. Naturally the easy integration between the service desk and the software issue tracking system occurs if you are using Atlassian, good luck with other tools.

Alternatives Considered

Redmine and Azure DevOps Services

Switched From

Redmine and Azure DevOps Services

Pros

The default settings for Jira Service Management allow you to maximize its potential right away, with nothing in the way of setup. It is possible to personalize it with a wide variety of settings so that it functions just how one would like it to.

Cons

Because our SSO implementation needs it, in order for a user to sign into the customer portal, they will first need to sign into the parent Jira site.

Pros

Jira's ITSM module is user-friendly and intuitive. You don't need much training to master it. One of the features I appreciate most is the ability to mention other people with @ in the comment section and keep them updated on the ticket status.

Cons

The IT asset management module is very complex and requires a lot of configuration to enable the basic features. The out of box feature in this module was not useful for my purposes. I had to set up the IT asset classes from the schema level, which was time-consuming and tedious.

Pros

Estimating the team's velocity can be pretty accurate when the users fill in their Story Points and the time to completion. Cards also provide a lot of information, team members can collaborate in the comments section and the ability to create sub-tasks is a big plus.

Cons

Jira can become overwhelming for newcomers, specially if there are no explicit policies on how to use it. Also, when marking tasks as Done, it feels the completion time fields are a bit redundant.

Pros

I like the analytics and incident management part of the Jira service desk management and of course the ease of locating tickets and updating them.

Cons

I feel like JQL is necessary for important searches which not everyone has experience with.

Pros

Jira is standard of IT industry for managing effective development and connecting it to other teams in the company.

Cons

Jira can be sometimes complicated which is expected considering the amount of feature it needs to handle complex business processes.

Alternatives Considered

monday.com and Asana

Reasons for Switching to JIRA Service Management

More features required for effective development.

Pros

JIRA is the most useful tool for my remote team. I love that I get a bird's eye view of the items and statuses of what my team is working on. I am able to get a quick summary of the items that will make this month's sprint. It also makes collaboration easier as the system promotes ownership, accountability, and progress.

Cons

I wish we can assign more than one user to a card or assign a whole team.

Pros

Jira Service Desk was very easy to get started with. You could literally sign up for it and begin using it within an hour. Ticketing system is very customizable and powerful. Customers can be added in bulk and customers can sign up for entering issues. We were able to create different projects (or service queues) so that customers could send requests for IT help, or administrative help, or help with projects. Each such project/queue had different fields. Metrics are all built into the software, so we can know how often Service Level Agreements were breached, who breached them etc. The sheer amount of customizability is a joy. However, without discipline and thoughtfulness, it is very easy to customize it the wrong way.

Cons

We feel that the price point could be lower and the speed could be a little faster. Atlassian has made improvements with speed. If a company had 5 people manning different queues and the issue volume is low, the cost would be ~1500/year for those 5 users. So, it would may not be cost effective for a small company that is watching their costs closely. We also felt that a Wiki is not built in. So, if a common solution needs to documented that spans multiple tickets, there's no way to do so. We could buy Confluence from Atlassian for an additional cost.

Alternatives Considered

Pivotal Tracker, Trello, Basecamp and Asana

Reasons for Choosing JIRA Service Management

Our previous solution was built on SharePoint. It was slow. Very slow. We had workflows that drove communication after an issue was entered. Workflows would break often with hard-to-understand errors and debugging them was difficult. We had to build all the reports surrounding data we collected from SharePoint. Most reporting surrounding SharePoint were manual. We spent more time debugging issues with SharePoint than the time we spent on the most demanding customer. Something had to change. We tested Jira Service Desk one day and within hours our customers were using it. There was a day and night difference between the two systems and customers were happy. Built in reports were excellent.

Switched From

Microsoft SharePoint

Reasons for Switching to JIRA Service Management

Asana has been working on improving the speed of their software. Their slowness has been well documented on various sites. Even their own team acknowledged and worked hard. We were not just read to jump into Asana due to the slowness. Trello was great - fast and easy to use. Reporting was missing. Pivotal Tracker felt like it was well suited for dev work and was comparable more to Jira Software. Basecamp felt like it was well suited for project work. Jira Service Desk fit the bill for IT help desk, admin help desk etc.

Pros

JIRA service management is very use friendly software in day to day project activities.
JIRA has been excellent tracking tool for testing bugs, defects easily during entire project cycle.
It is very effective place holder for IT asset management and project management phases.
JIRA has capabilities to integrate with multiple ITSM management tools and reporting tools for effective reports and dashboarding.

Cons

New changes for html pages take little more time for loading when moved to production.
Version controlling sometimes create hiccups during rollback period.

Alternatives Considered

Confluence

Reasons for Choosing JIRA Service Management

JIRA is more user friendly and easy to mange across enterprise compared to Excel. Macros behaviors were pain points during maintenance but JIRA resulted as cost effective tool for corporates model.

Switched From

Microsoft Excel

Reasons for Switching to JIRA Service Management

It is more cost effective and user friendly software compared to Confluence. It is easy to track for scrum stories and follow agile approach to avoid standard documentation hours

Pros

The native integration with JIRA software management and business management project boards make ticket triaging and documentation straightforward and low effort. Aside from the initial setup and instrumentation of the integration points and framework (configurable for different org sizes), using JIRA Service Management enables speedy triaging and processing of requests across IT, software, product and business, and service teams.

Cons

There are idiosyncrasies to the JIRA UI (which is shared and consistent with JIRA software, business project management, and Confluence) that can be confusing at times with subtle UI elements that are not always straightforward to the end user. At times, it can be confusing switching between the different JIRA apps that your org uses.

Pros

JSM really doe make things very easy to do from ticket management to full blow products with customisable screens and input. It's worth the money but can get expensive when the whole company decides they want it.

Cons

Really only the price is the con here, it's expensive but worth it. They offer fixed subscriptions which save money but cap users or pay as you go which costs more, but users can be added and removed ad-hoc.

Pros

JIRA Service Managment is have lots of customization capability & also ready made template is also good. Ready made report is good but for accurate details need more tuning to the reports or create own customize report.

Cons

When reporting things come in picture that require customization. Also standard ticket type is not good enought for day to day use. So to configure all these need require experience user or consultant to understand your need & configure it.

Pros

Scalability.
Flexibility to be tailored to particular organizational needs.
Very rich in terms of features.

Cons

Setup can be made a bit simpler.
Could use more ready 'templates' that can be used to quickly roll out the product for production.

Pros

Jira Service Management itself, is a robust service management tool that offers a wide range of features and capabilities. Some of its key strengths include its flexibility and scalability, which make it an ideal choice for businesses of all sizes. It also offers powerful automation capabilities, allowing users to streamline their workflows and improve productivity. In addition, Jira Service Management provides detailed analytics and reporting tools, giving users valuable insights into their service operations.

Cons

Of course, like any software tool, Jira Service Management has some potential downsides. For example, some users have reported that it can be difficult to set up and configure initially, especially for organizations with complex workflows or service structures. Additionally, some users have found the interface to be somewhat complex and overwhelming at first, although with time and experience, most users find it becomes more intuitive.

Pros

- Powerful project tracking: it provides an extensive range of tools and features to effectively manage software development projects, including issue tracking, task assignment, and progress monitoring.- Customizability: The software allows for extensive customization, enabling teams to adapt it to their specific workflows and requirements.- Integration capabilities: it seamlessly integrates with various development tools and platforms, facilitating collaboration and enhancing productivity.- Reporting and analytics: it offers robust reporting and analytics features, providing valuable insights into team performance, project progress, and issue resolution.

Cons

- Steep learning curve: Due to its vast customization options, JIRA can be initially overwhelming for new users, requiring time and effort to fully grasp its functionalities.- Complexity: The extensive features and configurations available in JIRA can sometimes make the software feel cumbersome, especially for smaller, less complex projects.

Pros

User friendly, easy to learn, integrates well with Atlassian eco system, roles based access control, licensed based on service agents

Cons

Dashboard and reporting gadgets can be improved further to provide better trend reports for the incidents, marketplace plugins can become overwhelming.

Alternatives Considered

ServiceNow

Switched From

Freshservice

Reasons for Switching to JIRA Service Management

Better pricing and Atlassian ecosystem

Pros

Creating a board in Jira, maintaining a Backlog items list, Creation of sprints. maintenance of sprint, Maintenance of team members and tracking the work done by the team are the services i like in Jira.Also the burn up and burn down charts provided by Jira are xecellent

Cons

The export to excel features can be improved in JIRA.

Alternatives Considered

Azure DevOps Services

Reasons for Switching to JIRA Service Management

Because of the ease of use .

Pros

It is a software to improve productivity, very good for ticket management, project management, incident management, it is perfect for monitoring and with good functions to improve the productive capacities of the different departments.

Cons

It is a product that the first users cannot use perfectly, but after a light training the user adapts perfectly, also the price is high but totally necessary, since the functions and the results are very good.

Pros

Jira service management is one of the best service desk softwares in the market. The ease of use is great, even for users new to the software. It helps the users keep a proper and clean track of the incidents/tasks/etc they have. One of the best things about Jira Service Management is that multiple teams can easily collaborate and work on it. This enables big projects involving various teams to work seamlessly.

Cons

There are not many major disadvantages with using this Jira Service Management software. But a user must be careful while deciding to delete a ticket, because once deleted it is goodbye for ever. It cannot be retrieved. This option can be modified to allow retrieval of deleted tickets to ease the process for users who might delete important tickets unintentionally.

Pros

Jira Service desk works great. We use it in a media company in all of the service departments to track requests from Media ingest, to graphic requests, to crew requests. Our producers can easily log in from anywhere and fill out customized forms for the type of service they are looking for. The department gets the request in seconds and can start fulfilling it right away. In a fast pace news world, this allows us to get what is needed for broadcast air done fast while keeping track of all the work we have to do.

Cons

There are some features that you would think would come right out of the box with jira service desk that doesn't. The only way to get them is to buy a plug-in from their market place. Some features that we would like to see is having the requester see who is assigned the order & allow them to request updates to their requests.

Pros

Jira Service Management is highly customizable, with a wide range of configuration options, add-ons, and integrations available. We create tickets on daily basis and also link it with confluence documents to track our workflow and tasks. Since its cloud based tool collaboration features, including real-time chat, comments, and status updates, making it easy for teams to work together. We also use to track performance and identify areas for improvement.It helps our team to automate routine tasks, such as ticket routing and notification, which can save time and improve efficiency.

Cons

Sometimes integration becomes difficult and also the company can solve this issue by providing video guides which can help the user to understand easily.

Pros

Ticket management has been a breeze for our teams as we were lacking one stop solution for all out team other than dev teams, every colleague in out company can now get their issues resolved as per there query and doesn't require any manual intervention.Its easily integrable with. JIRA so are teams can link tickets in case of any enhancement. The UI is quite simple and easy to use.

Cons

The initial setup was a little cumbersome due to multiple rules which we needed for our business, other than then there are no issues!

Alternatives Considered

Zoho Desk