JIRA Service Management Reviews

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.

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.

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.

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

Most important functions, from perspective of scrum or devops team member, can be learn quickly and used easily. Also it gives a lot of option of organizing workflow between many agile teams. You can have different levels of tasks - and visualizations to them. I like that you can organize many boards and link everything. It takes of course a little bit of consistency in following the rules in order to not create a mess.

Well, it tends to have sudden downtime.. for no reason (well at least from my perspective) it’s not responding. Speed interface could be improved. Sometimes you have to wait a while after an action performed.

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

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

I find the UI of Jira Service Desk very clean and modern compared to other service desks software on the market. Included with the service desk is a customisable user-facing portal for users to raise tickets in, which proved very popular with staff when raising tickets alongside traditional email tickets. Due to the way Jira splits service desks into different projects, we were able to create service...

Read more

For a service desk technician using Jira Service Desk the back-end UI for managing tickets can be a little overwhelming, however this can be fixed by editing the default workflows for tickets to hide not required information and details. The administration settings are somewhat unintuitively set out for system administrators, but once you get to grips with the layout it becomes easy enough to find what you need from the settings page. We found the instructions on the Atlassian website for setting up an external redirect with a custom URL in IIS a little sparse on detail, but a quick trip to the Atlassian forums cleared up any queries we had with the process.

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.

The ease of use and anybody can use the tool for Ticketing, project management, issue tracking, dashboards etc...

The options are at times clumsy and confuse the end users when the data is too much.

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.

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.

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.

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.

Definitely the collaboration and bug tracking tools. Email notifications are also very convenient and lead directly to the relevant issue. The export of open tickets with their status is also useful for internal team reviews

The ticket filtering tools you are responsible for or involved in are not optimal, especially in very complex projects. The general usability of the platform is also not very intuitive with many fields to fill in that are difficult to understand.

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.

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.

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

Read more

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.

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.

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.

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

Read more

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

Read more

The platform offers a wealth of issue tracking features, reports and metrics that make it easy to monitor productivity and identify areas for improvement. In addition, the self-service portal and integrated knowledge base provide end users with useful resources to resolve issues on their own, reducing the support team's workload. Support for process automation is also impressive, enabling the implementation of automated rules and actions to streamline and optimize workflows.

Despite its many advantages, JIRA Service Management can be complex and difficult for new users to learn. Initial setup and customization takes time and effort.

Jira is a good tool , we used it mostly for Product Management based work due to it's easy to share and easy to grant access features I find it ideal in a Product based environment and that is where it shines best . (decent pricing , good collaboration , good reporting )

At this price point , you have a lot of variety and the market becomes very competitive , you can go other options if you have a Support department for example , if money is no option than this can also fit that role , however the additional features that Jira offers I feel might be lost on support.Summary : Great for Product , Medium for Support

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.

Integration was fairly easy, we use Service Management alongside Confluence, BitBucket, and Jira Software and having it integrate with our Confluence Knowledgebase is really helpful. The automation options are also extremely useful when new tickets are created.

Jira Service Management isn't the cheapest piece of software to use, third party integrations can be a bit unreliable, having to pay additional subscription fees for third party integrations isn't great.

JIRA Service Management is fantastic tool as it provides IT service management capabilities, allows businesses to manage IT incidents, problems, and changes. It helps to improve the efficiency and effectiveness of IT operations, reducing downtime and improving service quality. It offers customer support features, to track and manage customer requests and issues which reduces the workload on customer support teams. The amazing feature is, it also includes Agile project management capabilities, which allows businesses to manage projects using agile methodologies, as it increases project visibility, collaboration, and delivery speed.

Jira Service Management can be slow to load and can sometimes experience performance issues.

When you use this application as an addition to JIRA, it is a great tandem. I adviced my company to use Service Desk when we were discussing how to receive bugs and ad-hoc requests. We are using this application fro several years and we do not think about changing it.

The only bad point that I can mention about Service Desk is its price. A lot of clients I worked with complained about it. They manage really carefully the number of users that are Agents (users you actually pay for), and get really upset if they were not carefull enough and their bill was higher then they expected.

I like that JIRA can be as simple or as complicated as you want it to be. I like that I can customize my dashboard and menus to my own personal liking and needs. It also helps engineers to sync on ticket requirements pretty easily.

JIRA can be complicated, but it doesn't have to be. I think there is a learning curve if you want to go beyond doing the basics, but I personally like to keep my workflow with JIRA pretty simple.

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.

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

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.

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.

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.

Assign each individual task according to the priority and track all the work done by all the individuals working on assigned tasks including time taken.

It's very hard to learn new features of Jira. Even after working for so long lots of features are very hard to use in Jira. Plus the pricing plans are very expensive compared to other project management tools.