JIRA Service Management Reviews

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).

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

First of all, Jira allows us to manage customer support requests in an organized way. They can be tailored to individual squads and relatively easily monitored. All relevant details can be stored in one location in a Jira request. Jira is an easy-to-use tool and request tracker for teams, with features including customizable dashboards, access permissions, and time/effort monitoring.

Inadequate translation of Jira Service Management into other languages is one of its biggest drawbacks, as it results in an unnatural hybrid between English and the selected language.

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.

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.

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

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.

Works so well with a support email ID to collect client helpdesk issues, and even link them to development (IT project) tickets

Perhaps the dashboards can be easier and more insightful, for checking workload, number of issues managed per staff member etc

Jira Service desk is the help desk add on for Jira. It's great because it seamlessly integrates with Jira. If you're on Jira already it's a natural extension.

It's not really viable as a stand alone product but as part of the Jira ecosystem it's a nice add on. Quite steep learning curve.

Its flexibility. It's a simple statement, I agree, and you're probably reading this wondering why I'm being so vague. But JIRA software is a bit hard to summarize simply because it's just so flexible. There's no "correct" way to use it.

It's rest API is pretty powerful too and very easy to extend Jira to "integrate" with 3rd party applications that doesn't have an official Jira integration.

Creating workflows can easily become very confusing and you can easily break how your projects in Jira work if you aren't careful. With every Jira production license you also get a free dev license so that you can set up an isolated dev/staging environment. This is invaluable and highly recommended. The downside is that there is no easy way to migrate any of your changes from dev to production. But there are 3rd party plugins for that.

- JIRA is very simple to setup & deploy for beginners & can also be used very effectively by advanced users- Has integrations with other tools- JIRA helps report, manage & track bugs, product features via tickets in 1 place- JIRA has history of tickets, work logs, etc that help document projects & promote overall accountability

- JIRA can be expensive for small companies & small teams- JIRA needs licenses for users just to view the JIRA board & tickets

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.

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.

Flexible and customizable: Jira is highly customizable, allowing users to adapt it to their specific workflows and processes. This makes it a great tool for teams with different needs.Great for agile teams: Jira is well-suited for agile methodologies, such as Scrum and Kanban. It provides features like sprints, backlogs, and boards that can help teams manage their work more efficiently.Integration with other tools: Jira can be integrated with a variety of other tools, including GitHub, Slack, and Confluence. This makes it easier for teams to collaborate and share information.Powerful reporting and analytics: Jira provides powerful reporting and analytics features that can help teams track their progress and identify areas for improvement.Large user community: Jira has a large user community, which means that there are plenty of resources available for users who need help or want to learn more about the tool.

Flexible and customizable: Jira is highly customizable, allowing users to adapt it to their specific workflows and processes. This makes it a great tool for teams with different needs.Great for agile teams: Jira is well-suited for agile methodologies, such as Scrum and Kanban. It provides features like sprints, backlogs, and boards that can help teams manage their work more efficiently.Integration with other tools: Jira can be integrated with a variety of other tools, including GitHub, Slack, and Confluence. This makes it easier for teams to collaborate and share information.Powerful reporting and analytics: Jira provides powerful reporting and analytics features that can help teams track their progress and identify areas for improvement.Large user community: Jira has a large user community, which means that there are plenty of resources available for users who need help or want to learn more about the tool.

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

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

Easy to set up and deploy, configuration is relatively easy, the platform is stable and performant.
There is a good 3rd party marketplace for additional apps that can be installed.
Security options like SSO are available.
Customer Support is responsive and knowledgeable.

Reporting on SLAs is poor, overall reporting is ok but could be better.
Costs ramp up significantly as Atlassian Access is required if you want SSO, this is an addtional charge per user.
The pricing is done on a per user tier level e.g. 101-200 users is a price so you have to pay for 200 user accounts even if you only have 101 actual users.

It has a very high adoption rate and big user base, therefore there are a lot of tutorials on how to do some certain things with Jira Service Management. That's a big advantage.

Nevertheless, quite a few features JIRA Service Management can enhance. For instance, the search engine of the whole JIRA is not yet powerful, although it is expected to be powerful because it's a system that administrates a large number of tickets. Searching using text often results in poor results. Additionally, it is currently not possible for searching for some phrases that belong to a hyperlink that is hidden inside a text.
Additionally, it is not yet possible to create a new type of relationship that links an issue with another issue. Currently one can only choose from a dropdown of relationship types that are already available there.

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.

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.

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.

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.

Jira allows us to track individual issues across the organization accurately by assigning unique identifiers. It allows us to effectively manage our issues using groupings(epics), Releases, and sprints.

Starting new projects on the SAAS is a bit tricky to get it to match older configs you are interested in as it is geared towards kickstarting new users.