JIRA Service Management Reviews

Here in Korea, there's high demand for eCommerce solutions or platforms. You'll see fifty percent of products on eCommerce platforms or follow an eCommerce model. Some companies even own eCommerce platforms. For example, a clothing company wants to sell products online and uses online services. Usually, companies want to build platforms, so my company goes ahead and helps build the platforms, and Jira Service Management helps in the process.

Another use case relates to training solutions, especially with the COVID-19 pandemic. A company wants a training platform for its employees. For example, a rental company with thirty thousand service staff or installers must train employees frequently or regularly, so my company does the application development for online training solutions.

My company also uses Jira Service Management in platform-enhancing projects. For example, a company wants to enhance CRM or ERP, manage or improve hiring, do cost management, etc.

Jira Service Management is a generic solution that helps in project management and application development projects.

Jira Service Management has three features I found valuable. First, it has a workflow feature that you can configure for your specific requirements. For example, you can configure your workflows for service management, especially if you want to utilize it for a service desk. This is beneficial if your company provides services to customers where customers or users have questions, complaints, or troubleshooting requests. Through Jira Service Management, you can receive service requests and handle the requests within your organization or company as long as you configure and apply service management processes through the solution. This would still depend on your company's process. It's different from one company to another.

Another feature of Jira Service Management I like is that it lets you efficiently manage service requests with team members or employees. Team members can access and handle designated service requests, add answers, check the history, etc.

Jira Service Management also has a dashboard that helps you handle service requests well. Dashboards provide monitoring information, such as the number of service requests, which customers need information on, who's handling the service request, what's the status, and the priority levels of the requests. You can get service request statistics on the dashboard.

I also like that Jira Service Management has several feature sets you can configure. You can add columns and configure screens containing the information you want, such as customer name, environment, etc. The solution is flexible, which I also find valuable.

What's missing in Jira Service Management is the user screen. You'll find it very weird if you've never used the solution before. You won't instantly understand how to use it. It's not too difficult to grasp, but first-time users would think that Jira Service Management is a weird solution. The user-friendliness of its interface needs improvement.

There's a pro and a con to adding user screens because some people might lose product visibility if a user screen is added, but I want Jira to develop a way to add user screens to Jira Service Management.

I started using Jira Service Management in 2014. I've been using it for eight years now.

Stability-wise, Jira Service Management is a nine out of ten because it's been stable for eight years.

Jira Service Management is very scalable, so I'd rate its scalability as nine out of ten.

My rating for Jira Service Management technical support is eight out of ten.

Positive

I find the initial setup for Jira Service Management very convenient. Ten minutes is enough for me to set it up. In terms of users becoming familiar with the solution, it would take one week. The total time to deploy Jira Service Management is one to two weeks; setup-wise, it's eight out of ten.

How you set up and deploy Jira Service Management depends on your needs. Sometimes you need to set the solution up with a CI/CD pipeline to streamline it. You must gather your requirements and look into your project scope, particularly application feature sets and development list. Once you have the requirements, you can drill down into the development list, break down the sub-functional list, and then identify the software design.

From the software design perspective, you need to break it down into functionalities, and once you have your functionality list, you can assign that to developers and designers. The designers and developers can work via scrum or sprint. My company practices both. People will then develop the software based on the application functionality list and perform some tests.

The QA department will then do an API test and test the user interface and feature sets. Staging, verifying, and validating requirements will also occur before the software is deployed into a production environment.

As Jira Service Management lets you enjoy efficiency and more visibility compared to other solutions, you can consequently save money, so there's ROI from the solution. Still, at first, there were some deductions.

ROI-wise, it's a seven out of ten.

Jira Service Management has affordable license fees. It's $12 a month per person. If you need support, you need to email Atlassian. Atlassian doesn't provide premium-level support that requires additional payment. My company doesn't need it anyway.

I'm a heavy Jira and Confluence user and have a lot of information on system integration projects. My company used ALM solutions ten years back, but not now. I'm looking for other solutions that provide quick delivery for digital transformation projects, as that's what companies search for nowadays.

Confluence, like Jira Service Management, is from Atlassian. Atlassian provides several solutions, such as service management and application lifecycle management (ALM) solutions.

I use several solutions, such as Jira Service Management, Jira Work Management, Confluence, Bitbucket, and Trello.

My company uses Jira Service Management heavily for sixty projects.

My company is a service integration company, so for some customers, Jira Service Management is deployed on the cloud, while for some, it's deployed on-premises. My company builds CI/CD pipelines for customers with data centers. My company utilizes Jira Service Management heavily in both AWS and Azure. The solution is deployed on Azure or AWS, depending on the customer's requirement.

Three people train users on the software. It's not difficult to set up Jira Service Management. The difficulty occurs when users have no familiarity with managing the solution. A small software development team sometimes doesn't want to use Jira Service Management.

When the solution is up, it doesn't require maintenance. If it's just a feature upgrade, it doesn't need maintenance. However, sometimes, my company needs maintenance and support because the project is continuously evolving, so there's a need to make some changes. For example, you need to change your workflow or the dashboard. Atlassian maintains the software. It's Atlassian's responsibility. My company has three engineers for ALM maintenance, rather than Jira Service Management maintenance. The three engineers support customers.

My rating for Jira Service Management is nine out of ten.

My company is a Jira customer.

We use JIRA Service Management for any issue coming into the store and have four escalation levels. We're also using the solution for KPIs, both in the cloud and on-premise deployments, but in the server version, there are more add-ons, such as the SLA and dashboard features.

One of the main benefits of JIRA Service Management in my company is the SLA. I also saw improvements in problem management and request management. The solution also competes with ServiceNow ITSM, a good platform.

I find all features of JIRA Service Management valuable. It's a helpful solution, and it's necessary for my company.

The automation feature in JIRA Service Management is also beneficial, and that's yet to be available in ServiceNow. ServiceNow doesn't have the flexibility to automate processes.

I created one ticket in 2017 and followed up, but there's still no confirmation or resolution for it, and this is an area for improvement in JIRA Service Management. The ticket was about some enhancement to the customer portal that shows the assignee and SLA, but it's still not developed. The view of the customer is still limited. What would make JIRA Service Management better if the ticket had more details, such as resolution time, whether the ticket was breached, etc.

What I want to see in JIRA Service Management in the next release is related to add-on features, where if I need a new feature, JIRA requires me to pay for all users when only specific people use that add-on. If only a few users need the reporting feature in JIRA Service Management, I should not have to pay for everyone. I should only pay for the specific users who require reporting.

I've worked with JIRA Service Management since 2012, so that's ten years or more.

One to two times a year, my company faces some JIRA Service Management stability issues, though it isn't entirely because of the solution. The problems sometimes arise from storage or hosting, which means my company should upgrade the version, and that's it.

Scalability-wise, I'd rate JIRA Service Management eight out of ten. I see a lot of improvement on the cloud version that isn't available on the on-premise or server version, and I know that JIRA no longer sells the server license.

The technical support for JIRA Service Management is good and answers on time. The support team also gives sufficient information about the issues, so I'd give support a nine out of ten.

Positive

Anyone can set up JIRA Service Management. It's not complicated.

My company started with JIRA Cloud and then moved to JIRA Service Management. It took around six months to migrate from the old version to the new version because my company tried to use all features of JIRA Service Management first.

My company installed a new version or instance, then migrated the tickets from the old server to the new server. What took time wasn't the installation, but the process of rebuilding and enhancing workflows, configuring automation, and customization to meet different requirements.

I initially asked for help from one partner in deploying and configuring JIRA Service Management, and then my company managed everything afterward. One or two others did remote sessions to help with scripting during the deployment.

There's ROI from JIRA Service Management. The solution decreased the emails and calls we received about issues, so we require all users to log everything in JIRA Service Management. We use the platform in all departments, such as Finance, HR, and Procurement. We even use JIRA Service Management for any workflow, even those needing approval or escalation, because we get ROI from it.

The price for JIRA Service Management is reasonable and cheaper than other ITSM solutions, but the licensing model is different, so you cannot compare it with other solutions. Overall, the pricing for the solution is acceptable.

My company has JIRA Service Management both on the cloud and on-premises.

I'm using the latest version of JIRA Service Management in the cloud, but I can't recall if the server version is 7 or 8.

The solution doesn't require maintenance after deployment. Still, my company has a maintenance contract with the vendor if the need for script customization arises, but for maintaining workflows, that's managed by my company.

The company has around two thousand agents on JIRA Service Management, but the number of customers is three thousand to four thousand. The number of users increases daily, but my team only gives them the customer view, so my company's current usage is enough.

I'd recommend JIRA Service Management to others.

My rating for the solution is eight out of ten.

I mainly use JSM to pick solutions for customers, for email to case, and for self-service tickets.

JSM's best feature is the integration with other Jira products.

JSM's ability to handle large volumes of emails isn't great. Its SLA management is also very primitive and should be made more robust. In the next release, JSM should include the ability to send single emails to large enterprise organizations rather than each individual receiving a separate message. 

I've been using JIRA Service Management (JSM) for three years.

The cloud version is stable.

JSM's cloud version is scalable, but you need to be cautious with the on-prem version since you will be onboarding thousands of additional customers to support.

I previously used Salesforce Service Cloud and BCM software.

The initial setup is straightforward, but the software doesn't give any help, so you have to use third-party tools like script and SLA management tools.

JSM's pricing is one of the best, starting at around $10 per user, per month, with volume discounts available.

I advise anybody looking into JSM to ensure they get their workflows right and plan strategically about how they want to integrate their standard product with JSM. They should also stay away from the on-prem version. I would give JSM a rating of seven out of ten.

On a daily basis, we're working on migration activity. Apart from the migration activity, we're working with the modifications and workflows for particular people who need to approve activities - those who are doing user management and customization. We are doing some scripts on the create screen as well. Whenever there is an approval, it may require setting some features that hide things automatically or some features that need to be filled automatically. We have Lambda in the AWS. In Lambda functions, all the fields in JSON format need to be triggered in Jira. 

I like Scriprunner. Whatever is not possible, we can make it possible through Scriptrunner. We can customize the scripts, et cetera.

The initial setup is pretty easy.

While I really like Scriptrunner, there are behaviors we don't have in the cloud. In the cloud version, we need to do scripts and evaluators only. We don't have behaviors in the cloud. They need to do some updates in the cloud in future releases.

For example, we have ten custom fields in the data center create screen. If you select the first custom field, it will drop-down automatically the following nine custom fields that need to be changed. Any unwanted fields need to be hidden automatically. When we use the behavior, it is in the data center server version. However, working on the cloud version, we don't have that behavior feature in Scriptrunner. We must go with the validators if we need to write any scripts in the cloud. 

Basically, the cloud and the server aren't identical. They work in slightly different ways and the new cloud isn't the same as the server.

I'd like to update the dashboard so that more features are available. 

I've been using the solution for the last five years. 

The stability is okay. We do get bugs. However, we can figure it out. 

The solution is scalable. You can add users. 

We have a license for 10,000 users. However, only 8,000 people are using it. If users are not using it for 15 days, we'll remove them.

I work on technical support. We have low priority, medium priority, hybrid, and critical tickets. The simple tickets we'll assign to junior-level people if we have any. If the bandwidth is less, then we'll take the tickets. If bandwidth is more, then we'll assign the tickets to the lower-level people. However, in general, we deal with support queries. 

I have years of experience with Jira and have a good level of knowledge. 

Positive

We had ticketing systems from ServiceNow and YouTrack. Compared to Jira, the tools are not very good. For example, if you take the workflow only in the Jira, the workflow will be simple. However, with the other tools, workflows can be a bit complex. They need to write some Java code, for example. There is some complexity. They are also not that economical compared to Jira in terms of pricing. 

It is not complicated to set up. It's pretty straightforward. I can set everything up in about two hours. However, if any customization is needed in the database, it will take some time. It depends on the customization and the client as well. 

Some clients don't want any customized as well. They want only a simple setup. What we'll do is we'll install a server. We'll do the project's setup, explain everything, and show the server customer the base we have. Based on the blueprints, we'll create data servers, et cetera, and they'll use the simple workflow.

Going forward, they'll learn how to use Jira by doing. Once they know Jira, they'll ask for the customization part. 

We can handle the initial setup.

It is worth the money; however, if a company has budget complications, they should start with a standard version. 

The price of Jira is very good. 

We have a standard basic version. We also have premium plans we have in Jira. The cost depends on the plan. It also depends on the number of users and plugins. 

A basic plan will charge $10 per user. A more premium plan will charge $18 per user.

We are Atlassian partners.

We have a cloud version, and we have a data center as well. In the cloud, we are doing migration activities. In the coming next two years, when it comes to the server, there is no support and therefore, we're planning to completely move to migrate to the cloud.

If you are using this software for the first time, I would suggest the use of the cloud instead of a data center server. I prefer to use the cloud due to the fact that, in the coming two years, the server won't have that much support. Everyone is moving to the cloud and it's developing daily. The automation is inbuilt in the cloud compared to the server as well. Of course, for automation, you will have to pay.

We do find the cloud more secure and there are updates happening day by day. It's becoming more robust.

I'd rate the solution eight out of ten. If they improved their API integrations, I would rate it higher. 

We upload the tasks for the team, working with them, and they know the status of the tasks.

It helps with time management and team management of the new tasks.

The status of the tasks and the ability to assign any task to any person are valuable features.

It should be easier to log in. When I first tried to log into Jira, I faced issues accessing my company account.

I've been working with Jira Service Management for the same duration as Wazoo, which is about three months.

I would rate the stability a nine out of ten.

All of the teams in the company love Jira. 

I didn’t need to call customer support.

Positive

I didn't work with other log management tools before, but I know some information about platforms like Splunk, IBM QRadar, and others.

For Jira, the setup is good. It is an eight out of ten.

I was not involved in the implementation.

I did research about platforms like LogRhythm, Splunk, and IBM QRadar.

I recommend Jira Service Management. It helps with time management and team management of the new tasks.

I would rate it a nine out of ten.

We use Jira Service Management to open support tickets, follow up on those tickets, and monitor the work log. We also perform some report filtering to follow up on outstanding issues. We utilize Jira Service Management's features to track the status and use customized workflows for incident management.

Jira Service Management allows us to customize dashboards to retrieve real-time data. By defining filters based on different customer types and service types, we can monitor and manage incidents effectively. This high level of customization aids in decision-making and increases visibility in tracking issues.

We have found the issue type feature particularly valuable, as it provides an out-of-the-box solution that aligns with our needs. We also appreciate the ability to customize the status workflow, surface type, and associated features, offering us high flexibility and visibility.

There is room for improvement in the user interface and the queues. Currently, the queues, which list all issues, do not allow resizing of columns and appear primitive compared to filters. Enhancing the queue interface would align it more closely with the sophisticated filter reports.

We have been using Jira Service Management for one year.

Jira Service Management's stability is very high. We have not experienced any downtime, which ensures uninterrupted operations. The performance is excellent, contributing significantly to our IT operations.

The solution is highly scalable, allowing customization and usage across different platforms, such as desktop and mobile. We haven't yet explored all features, such as allowing users to submit their tickets, so there is plenty of room for scalability in the future.

The customer service and support provided by Jira Service Management are excellent. During my setup, I encountered difficulties, and the support team responded very fast and was very helpful in resolving my inquiries.

Positive

Previously, we did not use any different solution for these use cases.

The initial setup of Jira Service Management is rated a five. There is a learning curve that needs significant time investment to understand and configure the system. However, once the platform is understood, usage and configuration become much more straightforward.

I handled the deployment process myself. Our team of six users, including myself, required involvement during the setup phase.

Jira Service Management offers high ROI due to its subscription basis and cost-effectiveness. It does not require installing a server, as it is cloud-based, further enhancing its value.

The pricing for Jira Service Management is reasonable and not expensive. It feels fair because there are opportunities for discounts through resellers.

We did not evaluate other solutions because the decision to use Jira Service Management was made by my boss.

The most time-consuming part of the setup process is learning how to customize workflows. It is crucial to thoroughly read and understand all documentation and materials provided, which significantly aids in setting up and customizing the platform.

We use JIRA for user support, specifically first-level user support. 

Additionally, we use it to plan project steps. With the Carbon dashboard, it is possible to break the project into multiple steps. You can review what is done, what is set to be done, and what has been completed during the predefined time slots. For ITSM processes, we primarily use it for access processes. 

We also utilize its automation capabilities, such as automatically creating JIRA tickets from monitoring tools during batch execution errors.

JIRA allows us to easily monitor what the team is doing and which subjects team members are working on. The dashboard feature enables us to see task statuses and facilitates task management through drag-and-drop functionality. This has improved our productivity by making it easier to track tasks and team activities.

The most valuable feature compared to JPS is that JIRA is focused on user support and project management. It is easy to communicate with end users through the application, and for specific tasks, it's possible to break them into smaller tasks and link them together. Features like the dashboard and drag-and-drop functionality for updating task statuses make it user-friendly. 

The ability to create a Deep Bucket branch or link tasks from JIRA to another JIRA is also beneficial. Automation capabilities allow for automatic ticket creation using monitoring tools.

It would be beneficial if we could turn comments into subtasks or other JIRA tickets directly. If this feature could be added, it would enhance the user experience.

I have been working with JIRA and ServiceNow for the past three years.

In our environment, JIRA is very stable. We have different JIRA instances for testing, and with our architecture, the application remains stable except during major changes or updates. Daily operations are smooth and fluent.

As an end user, I find it difficult to comment on scalability. However, our dedicated deployment team manages the architectural aspects to ensure scalability.

I have not had any interaction with JIRA's technical support, so I cannot comment on their customer service.

Positive

Previously, I worked with GLPI for about six years before switching. I stopped using GLPI because I changed jobs and moved to a position that uses JIRA and ServiceNow.

From my point of view, as an end user, the initial setup was slightly challenging due to the new user interface compared to GLPI. However, over time, it became more user-friendly, and I discovered many good options.

A dedicated team focuses on maintaining the JIRA infrastructure. When new options are needed, they evaluate and include them, making the experience better for end users.

We have seen improvements in productivity since it is easier to understand team activities and task statuses through the JIRA dashboard. Comparing task management features, JIRA significantly outperforms GLPI.

I do not have information about the pricing or licensing cost of JIRA. The last time I checked, there was a cloud version available for subscription.

For a small enterprise or team, GLPI may be a suitable option due to its free version. However, for a larger, more stable, and highly improved solution, I would recommend JIRA. I'd rate the solution eight out of ten.

Jira Service Management was a plugin and was not a completely different tool. Earlier, it was just a plugin for regulation. Later, they introduced it as a different tool. Earlier it was known as Jira Service Desk, and now they introduce it as Jira Service Management, a different tool.

If you have a product-based organization, then people used to use it for interacting with the client and getting the requests from the client. If it's internal, there could be a Help desk, IT service desk, or finance service desk, wherever you have to exchange the request between agents and the user base. You have to pay the license only for the agents, not all users. People can create their tickets free of cost. There, you get the portal, and any number of users can create their tickets, and only agents need a license to resolve their tickets and work on their tickets.

Earlier, people used to communicate using email. For a single complaint or for any single task, you are sending so much mail in a chain. If you have to search for any single item in that chain, you go into the first email to figure out where it started, how it started, what the resolution was, and what the discussion was. If you are using Jira Service Management, you can search for the tickets within seconds, and you get the whole history of that issue. It's much easier. There's more clarity.

The most valuable feature they offer is not to build in cost for every user. It's free of cost for your clients. It's free of cost for your internal users. Only, you have to pay the license for people who are going to work on it. If I take the example of an HR Help Desk, if it's an organization of 10,000 people, then 9950 people can log tickets free of cost, and only 50 people need a license to resolve their ticket, if it's a team of 50 people in HR.

The solution is stable.

It scales well. 

Feature-wise, they are improving day by day. I cannot ask for any single feature. We have to worry about how they are increasing their price. Atlassian will increase the price by 5% for most of the tools. It's getting expensive. 

The deployment can be a bit complex, especially for those who are not technical. 

I've been using the solution for seven years. 

The solution is stable. There are no bugs or glitches. It doesn't crash or freeze. 

You can scale the solution whether it is deployed to the cloud or the data center. 

While we might have up to 5,200 people using the solution, we do not require that many licenses, as only those dealing with the tickets are required to be licensed. 

We're using the product quite extensively.

Technical support has been helpful. I have found some bugs in the past, and they did a good job in helping us deal with them.

I am aware of ServiceNow as well. The UI is not as user-friendly, and it costs more. 

I cannot say it's too easy to set up. It is moderate for a technical user, and for a non-technical user, it will be a bit difficult. There are many things you have to configure. You have to configure the permissions and notifications for customers and agents differently. You have to set up the portal and many more things. 

The deployment will not take too long if it's on the cloud. The infrastructure is already ready for you. Since the server is closed, you only have the option of the data center if it's a data center. However, if you are going to deploy it in a data center, then obviously, it'll take more time.

You only need one person if you are deploying on a cloud and two or three people if you are deploying on a data center. If you are deploying on Linux, you may need someone well-versed in Linux. The cloud is an easy, fast deployment as you can do it in a few clicks. The data center takes more people and time. 

You cannot do it own. There are requirements the IT team is used to manage various items, including SSL licensing certificates. You have to get SSL certificates from them. The infrastructure is usually managed by IT, and you must host your instance there, so you need help from them. The implementation is usually a combination of two teams, both IT and non-IT.

We have witnessed an ROI. The solution has paid for itself.

You can choose either monthly or yearly licensing. The cost has recently increased. It might be around $20 to $25 per user license. 

You have three types of plans: standard, basic, and premium. If you need to configure it more, you have to use some plugins from the Atlassian Marketplace. For those, you have to pay whatever they may cost.

I'm a customer and end-user.

We use a few Jira tools across the organization. 

It is one of the best tools in the market right now. If you are looking for any service management tool, then you have to go for it. It's easy to maintain and easy to use. The user interface is very good. 

If you are in a client-based organization, your client will find it more useful as you can integrate with Confluence, and then you can deflect the users to the knowledge parts. You can create your own knowledge information on Confluence, and, without creating tickets, you can redirect your client or user to Confluence.

From there, they can get the information they need. It saves a lot of time for the IT team and empowers the users to do things by themselves. They do not have to follow up. They do not have to create a ticket.

I'd rate the solution nine out of ten.