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

One of the aspects I liked most about Jira Service Management was its exceptional incident resolution efficiency. The platform truly excels in streamlining the incident management process, enabling our team to respond swiftly and effectively to any issues that ariseWith Jira Service Management, we were able to create a centralized incident ticketing system that provided complete visibility into ongoing incidentsThe automation capabilities of Jira Service Management were a game-changer. We were able to set up predefined workflows and triggers, ensuring that incidents were routed to the appropriate teams and escalated as needed

Cons

While Jira Service Management offers a plethora of robust features, one area that I felt could benefit from improvement was its reporting capabilities. Although the platform provides basic reporting functionalities, there are certain areas where additional enhancements would be valuable

Pros

After latest update the visuals are quite pleasant.You can really construct complex filters if you know what you're looking for.Task IDs unfurl into links.Permissions are very granular (although complex and you won't understand how to use them).

Cons

Expensive.No obvious features or you have to pay extra: time tracking, dark mode, CHECKBOXES.

Pros

We utilize Jira to proactively guard against issues, notify clients when they are discovered, and monitor their progress and enhancements. Having the assignor's identity and that of the assigned person clearly shown also helps establish trust.

Cons

I had trouble finding older tickets or finding out who else had been assigned to the key I was working on; an internal chat function could greatly benefit those of us waiting for clients to respond to comments.

Pros

Works very well as a ticket system, it's very customisable and uses JQL for custom queries if you're inclined towards detailed reporting. Third Party Addins available online in their marketplace and bountyful automation features.

Cons

It's very difficult to setup requires alot of time and effort and the software is not userfriendly so if you're implenting for a team that isn't IT literate then perhaps include some extra training days.

Alternatives Considered

Freshdesk and Zendesk Suite

Reasons for Choosing JIRA Service Management

We outgrew spiceworks and required a real ticket system

Switched From

Spiceworks

Reasons for Switching to JIRA Service Management

Functionality was near identical it came down to price and the fact we already used Jira for our Dev enviroment.

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

Jira Service Management is a great value for ITSM. It provides a portal for an unlimited customer base, and agent access based on Jira core. It's also very affordable compared to other similar products.

Cons

The customer portal is great, but offers little out of box customization. To build an elaborate portal, you need to purchase some marketplace add-ons.

Alternatives Considered

ServiceNow

Reasons for Switching to JIRA Service Management

Much better affordability and user experience.

Pros

Pretty much everything to do with ticket management and notifications from our internal 'customers'

Cons

The search functionality could do with some work when looking for older tickets and the searching of 'similar requests'

Alternatives Considered

Zoho Desk and Zendesk Suite

Reasons for Switching to JIRA Service Management

More customization that some of the competitors but not so much so as to make it confusing to set up.

Pros

Easy to integrate with ZenSimilar to another program we moved away from, but far more robustAllows for better ticket assignmentMore comprehensive with better options for ease of use

Cons

Not much- there are a lot of buttons and options to use so until you get use do what you need as an individual or department, it's a bit complicated, but once you sort that out and find your niche, it's a great tool for trouble tickets.

Pros

JIRA Service Management is an effective service desk solution that has revolutionized our team's support process. With its powerful features, intuitive interface, and seamless integration with other Atlassian tools, it offers a comprehensive solution for managing customer requests and bugs.

Cons

i don't have any minuses to say about this product.

Pros

Jira is extremely customizable, scalable, and easy to implement when compared with other SD platforms. Out of the box, it can be used as a tool to track incoming requests, however, paired with the thousands of compatible plugins, it is unparalleled. Jira SD has allowed our HR team to take our daily operations to the next level, transitioning antiquated, clunky paper processes into a 100% paperless experience.

Cons

My only complaint is when custom fields are added, you have to update every field configuration you have, individually. This is extremely time-consuming when adding multiple custom fields in an effort to create "forms" within Jira.

Alternatives Considered

ManageEngine ServiceDesk Plus

Reasons for Switching to JIRA Service Management

Cost, ease of implementation, customization and scalability

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 Management provides a ton of tools to build out you customer portal and internal ticket platforms. It has filled all of the holes in our previous solution right out of the box.

Cons

It is built for large, multi-team organizations so much of the power is not needed for a smaller company who requires a custom build but without all the hierarchy.

Pros

Easily integrates with your already existing Atlassian software. Allows for a seamless flow between all other products and allows for easy crossover to keep everything in a nice and neat tidy place.

Cons

It takes a lot of work and elbow grease to get it set up in a way that works for your organization. There can be some learning curves as there is no out-of-the-box working way, but once the time is spent it will save you loads of time in the long run.

Alternatives Considered

HubSpot CRM, Intercom and Zendesk Suite

Reasons for Switching to JIRA Service Management

We are already integrated into the Agile Ecosystem.

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

- Lots of tools in one place
- Integrates well with other apps (especially other Atlassian products)
- UI is clean and user friendly (customizable to a sensible extent)
- Contains useful metrics that are easy to configure and gain reports from
- Has multiple layers of user settings available for custom configuration to correlate to preferred levels of access among agents, customers, etc.

Cons

- Email bounce in frequently fails (bugs?)
- Depth of Jira admin user knowledge required for strong mastery of this app; time consuming to acquire a reliable user knowledge (which is necessary to utilize the app with the least bit of efficiency)
- Help docs, support mechanism unreliable/outdated (needs to be fresh and current to be applicable to present version of app)
- Confusing settings requirements for some user modifications needs (esp. where mapping/editing workflow schemes are concerned)
- Completely inadequate amount of general helps/tutorials available outside of Atlassian (YouTube, Google search, etc. for example) which seems a bit suppressed by design. Atlassian offers extensive training, but at a premium cost.
- Costly for the overall effectiveness it provides, after factoring these negatives along with the user time required to really learn the application.

Pros

Newbies to JIRA Service Desk can get a service desk project up and running in less than 30 minutes. If your organization is already using JIRA for issue tracking, then having a help desk with Service Desk is a no brainer. It allows you to integrate software teams and IT teams better within the same ecosystem.

The benefit of JIRA Service Desk, when compared with other help desk tools, is the customizability of your workflow. You can set up a workflow to be simple (with Open > In Progress > Closed statuses) or complex (with other statuses like On Hold or Waiting for Customer).

SLAs are highly configurable, with the power of JIRA's JQL functionality. So one can conjure up a query to fit their SLA needs. With the addition of custom fields, a Service Desk administrator can create fields to capture important information to streamline the help desk process.

Having Confluence also provides more benefits in which you can integrate an existing knowledge base space to a help desk project and self-serve your customers.

Finally, being in the Atlassian ecosystem enables you to add additional functionality and enhancements with the use of Apps. There are close to 1500 apps available for JIRA, and many are constantly updated by the app developers.

Cons

Administering JIRA Service Desk (and JIRA in general) can be daunting for a new user. With a number of customizations that one can do in a JIRA application, there will come a time where there can be a performance impact on the environment if the application is not governed well.

The Customer Portal (customer facing interface) is spartan in terms of customization. You can only customize so much, but it is limited in terms of branding it to suit your company's design specs.

Pros

Can clone tickets, create linked issues Can create parent-child relationshipsOther Atlassian sw. products and modules are well integratedScreenshots can easily be attachedPossible to delegate close bulkily ticketCan mention colleagues to make them remember about the tasksOptions to connect 3rd party developmentsExport modes are greatCan connect an e-mail address for processing

Cons

Lack of dark modeRedirecting tickets with the old IDs sometimes weirdScheduled reports could be usefulSimple "User" mode/layout is not enoughUI is not that easy at first, still better then Salesforce.JIRA is a general ticketing tool I would say, but there are others focusing on more on a technical side, like HP SM9.

Pros

One of the aspects I liked most about JIRA Service Management was its robust ticketing system and incident management capabilities. The platform provided a centralized place to track and manage customer requests, incidents, and support tickets. The customizable workflows and automation features allowed for efficient routing and prioritization of tickets, ensuring timely resolution. The integration with JIRA Software also enabled seamless collaboration between development and support teams. Additionally, the reporting and analytics features provided valuable insights into team performance and helped identify areas for improvement.

Cons

One aspect I liked least was the initial setup and configuration process. As the platform offers extensive customization options, it required some time and expertise to properly set up and tailor it to our specific needs. The initial learning curve associated with understanding the platform's terminology and features could be a bit steep for new users. Additionally, the user interface, although functional, could benefit from some enhancements in terms of intuitiveness and user-friendliness.

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

It's a good platform to track issues that are being handled by each individual in a project. It also has the option for notification being sent out when an item has been resolved, closed, or has gone overdue.
If it's configured correctly to have a backup, the team members involved can always learn from the past incidences reported. This will ensure that the team leader will be able to identify recurring items, timelines it took for resolution, and the team member assigned to resolve such items. This ensures that such items are priority issues that need in-depth understanding for them to be resolved permanently.

Cons

As an organization, we have not been able to integrate Jira with osTicket, which our customer Experience team uses. This means we have two Systems, and at times this can be overwhelming to track issues on both Jira and osTicket.

Pros

The most important part of the Jira functionality is the availability to enable teams to create, update, comment, assign, and establish a clear channel, and expectations that are required to complete a project in an organized and efficient fashion, the feasibility of documenting and creating a project status report based on tasks, pre-defined or project tailored tasks.

Cons

I believe that graphical interface dashboards would help to be robust, meaning, more detailed information, and the availability to generate clear reports is always useful for clients that don't want to access Jira, and just want an insight dashboard or the Project Lifecycle.

Pros

JSD is relatively intuitive and easy to learn without needing tons of documentation. Initial pricing is attractive. A decent plugin community fills some gaps, but be expected to pay on top of the initial JSD pricing.

Cons

Many "obvious" features are either missing or do not work as expected.

For example: in many cases, once an internal user is added to an issue, they no longer receive notification about internal comments. This is completely unintuitive, unexpected, and has caused many people frustration: https://jira.atlassian.com/browse/JSDSERVER-3410

Another example: Email traffic about an issue is *always* public. Do not allow your staff to reply to JSD's emails as customers will also get emailed a copy! https://jira.atlassian.com/browse/JSDCLOUD-3499

The worst part is, despite there being a few years' of discussion, and new comments added monthly by newly-affected JSD customers, Atlassian has no comments on the issues.

In some cases a plugin (more $) can help, but in some cases even the plugin manufacturers can't help as JSD doesn't expose enough info in their plugin API.

Pros

What I did like the most about JSD is the fact that you have a customer portal, a way to track and view your tickets at any time.
You can customize the product to at very last detail without too much trouble.

Cons

The stability of the software can be a sensitive balance after you reach 500.000 issues created on your instance.

Alternatives Considered

Zendesk Suite

Pros

Jira has very useful tools for managing projects, in my opinion you exploit its advantages when they are big teams, its main advantage is the follow-up to the development and progress of the projects, the errors that arise during the development process and the management operational, it helps you see more, to improve development times and correct errors for your next project, also has free trials so you can enjoy its benefits.

Cons

The truth is that it is a very complete program, but I think your biggest benefit is when you are big projects, if you are a small team I think other tools will be better suited, besides the price is a bit high.