JIRA Service Management Features

1) We mainly used this tool to plan our tasks for the projects we were working on.2) Creating Sprint Cycles and assigning tickets for each issue is very convenient using JIRA3) We can see the progress made by the ticket owner in the ticket description.4) There is a very brief and concise Audit history which we can track to see how the ticket status has changed5) I like the customization feature for each team and each product. We can choose what statuses and workflow our ticket should go through and select and arrange them very quickly.6) We can even link the BitBucket repo link and confluence link with our JIRA ticket, which is very handy for developers.

It can be sometimes overwhelming for newcomers, especially when one is not that familiar with JIRA and its terminologies, and it does have its learning curve.

One of the things I like most about Jira is its flexibility. It can be configured to suit the needs of a wide variety of teams, from small development teams to large enterprise organizations. The software is highly customizable, allowing users to create custom workflows, issue types, and fields to suit their specific needs.

It can be overwhelming for new users. The user interface can be complex, and it can take some time to become familiar with all of the features and options available. Additionally, the different features can be difficult to find and access, which can make it hard for teams to work effectively.

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

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.

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.

We've been using Jira Service Desk for several years within our Technology team. I think this tool has all the right features when it comes to managing the day-to-day as an engineer. You can utilize the Agile Design Methodology and manager sprints really easily. In terms of ticketing for customers, that's a different story.

Jira Ticketing is a bit of a nightmare to build and run. Our use case was to replace Zendesk with it, and to be honest, it doesn't have the best features to act as a ticketing software for your customer base. Some features are really too basic or even missing from the instance which means you have to customize a lot and if you are not experienced in it, it can be daunting. There is little customization available in terms of how it is presented to customers so branding is extremely basic.

Easy to use, easy to configure, easy to train internal team members on how to use and set up workflow; great visualizations and ability to track and trend issues is unparalleled

There is not much that I dislike about the software. I guess what could be improved is potential integration with IoT products or IFTTT

It is very user friendly and it gets really easy to track your bugs and issues. You can easily create subtasks and manage your sprint.

Sometimes it gets really difficult to contact support team in case there is any technical issue.

Very easy to track your tickets, adjust them, prioritize and get full update.Using it as knowledge sharing base which is great and easy to work with.

Not easy to create specific reports that are not set by Jira itself

It is a very friendly software with different kinds of users, adding to this it would send alerts to your email to let you know that your request is being handled.

The only thing that I do not enjoy is that when you are loading a ticket you can not attach pictures or evidence, you have to do it in the comments and this takes more time

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.

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

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.

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

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

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.

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.

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.

JIRA offers a huge amount of features, from simple support tickets to project workflow planning. Our method of project management (agile) works brilliantly with this, we're able to assign work in 'Sprints' that match our real working week. The ability to link JIRA with other 3rd party applications is excellent, we've integrated it with our content management system and QA / testing software. The wide use of JIRA makes communicating with other organisations much easier, most support companies are at least registered here.

The pricing is rather expensive, its not too much of a problem for a large institution such as ours, but for smaller businesses this may be too much. The user-interface and general layouts really aren't intuitive, for a new user it takes a while to get their head around the various features and processes. It took a few weeks for even the more experienced developers to get used to it.

The right products by doing time management with the Jira community around the world.

We easily lose from some features that sometimes need to be complicated.

- Powerful Agile views: It supports both the Scrum and kanban Boards- We can create custom work flow based on the different use case- Road map feature is very useful for the view the project status at high level - Detailed reports

- The tool is hard to set up and not very much user friendly- The tool is in expensive side. - No idea management features to keep track of your ideas and plans - Some time it is taking large time to load.

I used this software when I worked on a technical support help desk. I liked that the dashboard functionality and the ability to customize your view. There is a variety of widgets that are supported that assist with efficiency.

Our company worked with a separate company that also utilized this product. We created separate incidents in both systems if their assistance was needed. We noted each ticket with the relationship to the other's Jira system. While working in two systems was a con in regards to ease of use, this is not a fault of the software itself as there are obvious security issues in linking two companies together.

JIRA Service Management is an incredibly powerful and intuitive tool for streamlining service management processes. It offers an extensive variety of features and customization options to ensure that user needs are met. The user interface is modern and easy to navigate, and the workflow automation and reporting capabilities make it easy to track progress and ensure that tasks are completed on time.

Though JIRA Service Management is incredibly powerful, it can be difficult to learn and navigate for users who are unfamiliar with it. Additionally, the cost of the software and the services can be prohibitive for some organizations.

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.

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

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.

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.