Jira Service Management (formerly Jira Service Desk, now including features from the former Mindville Insight, acquired by Atlassian in June 2020) is a service desk software that is purpose-built for IT, service, and support teams. The software provides everything IT and support teams need out-of-the-box for service request, incident, problem and change management. Jira Service Management integrates seamlessly with Jira Software so that IT and development teams can work better together. Users…
$0
per month
Jira Software
Score 8.0 out of 10
N/A
JIRA Software is an application lifecycle management solution for software development teams. It allows users to create, prioritize and track the progress of tasks across multiple team members, and offers a wide range of integrations. It is offered via the cloud and local servers.
We evaluated Remedy's ServiceNow as well as a few homegrown solutions (in SharePoint and in JIRA Software), and found that Service Desk's integration into the rest of the Atlassian suite of products was the best selling point. We already were licensing a number of Atlassian …
We used a MS product called SCSM which was very old and hard to use. The UI was rough and we had to find a lot of workarounds to make it work like we wanted it to. Service Desk was the main product we looked at since we already had JIRA and Confluence.
I think JIRA is best suited for IT tickets and service requests. Comparison is hard, but I use JIRA on a daily basis and I cannot think of a better alternative for the task we are using it for.
Sure there are other great service management products in the market. Since we use JIRA and Confluence heavily, Service Desk fits perfectly in the suite. As a brief example, after the customer creates a case, we can create an associated issue at JIRA for development team, after …
When I evaluated Spiceworks, it was not going to be replacing any ticketing systems. However, I did evaluate it and was not extremely impressed by the short demo I did. JIRA was selected because a branch of our company was already using it, so it made sense to consolidate into …
Zendesk is a similar ticketing system that our organization used before JIRA Service Desk. The main drawback of Zendesk was that it can only be used as a cloud service. This means that our company data would be living on the internet at the hands of their security team. Another …
JIRA stacks up very well in particular with Microsoft Team Foundation Server which I used extensively for 7 years. The transition I had to do to JIRA was seamless and they both compliment each other well.
ServiceNow has many of the same features of JIRA. Teams within the organization use both ServiceNow and JIRA, but we primarily use JIRA. We chose JIRA because it seemed easier to set up the linking of related tasks and projects together, but other teams have said the same thing …
There are other systems that perform well, but we always came back to JIRA. One of the reasons is that it has companion systems like Confluence that can integrate and be used with it. Another reason is JIRA can be molded to be many things, not just project management. For us, …
Jira Service Desk has similar or equivalent features to heavyweight competitors as HP Service Manager, for a better price. The highlight of Jira Service Desk, in my opinion, is that you can customize a series of visual boards that are tremendously useful for an agile and …
Compared to other products I have used, like, Fresh Desk Service or Manage Engine it has more features included per user and technician (others may require a license for each type). Portal setup can be integrated to the Confluence Portal for easy access to Jira for service …
We selected Jira Service Desk because we were already Jira users, and the price point was easy to absorb. Our experience as Jira administrators made it easy to customize Jira Service Desk to our needs.
I think JSD is better than all of the similar ones I have used because it allows for greater customization. It is also really geared to submitting bugs and enhancements, where the other products are more about the software development workflow and project management.
It's out of the box the best option I could imagine and by-far better than any custom-made tools I've otherwise seen. Also thru its modular setup, it can be extended and upgraded as you go so the system adapts to your changing business requirements. Only downside is - without Co…
At the time we chose JIRA Service Desk, we had been using GitHub to track project issues and features. We were looking for something that would add more project planning features and allow us to put more project information together in one place. JIRA succeeded somewhat in …
When we completed our merger with another company, they were already using Jira so it made sense for us to use a common solution. Their experience and investment with the package was a major factor in choosing it over our current tools and those we were researching for future …
I've tried many other systems and used them extensively in the past including GLPI with integrated software and computer inventory systems. Used OTRS for customer related ticketing (in comparison to using Service Desk for internal ticketing) and found the system not geared …
We tried to make Clarizen a ticketing system and it just wasn't built to handle all of the different scenarios we required. Hesk is very limited and an OK ticketing system for internal use with simple tickets, but does not offer the same level of customization as JIRA service …
Great to manage your issues in a clear and centralised way. If your development teams work with Jira, it will all naturally come together. Great way to manage the issues from end to end. - Very flexible if you have people who understands the set up and is able to configure it for your needs - Maybe not the best if you want something with very easy set up
The Jira software works well for managing scrum boards and allocating resources to a task. When your Epics and Issues are set up properly, it can give you a good idea of where your team stands and the trajectory of your project. It is not the ideal solution if you need to provide documentation and support to people outside of your product teams or organization. It would benefit from having a public documentation or repository feature.
Ability to control the number of email notifications received (Note: this is a new feature in the Latest release but I personally haven not extensively looked at it and how well it solves the existing problem).
No way to reply to multiple tickets at once, say you got 4 tickets in for the same issue, there is no way you can reply to them in one stroke. Other Ticketing systems do have this ability.
Using a large number of add-ons to customize and add additional features adds up quickly and can become rather expensive.
Request forms are very basic and there is no native dynamic field ability available.
This is because Jira Software generates a huge profit for an affordable price. Having a tool that makes team management transparent and effective is very valuable.
In addition, the renewal of Jira Software and all Atlassian tools is predictable and clear, as the prices are published on the Atlassian website and there is no pyramid of intermediaries.
I gave JIRA a score of 9 since I am happy with the service it offers. I can easily see the SLA since it gives me visibility. I can pull up the reports I need. I can reach out to our clients using the PR ticket so it is hassle-free for me.
JIRA Software is a pretty complex tool. We have a project manager for JIRA who onboarded us, created our board, and taught us the basics. I think it would have been pretty overwhelming to learn without her. JIRA offers so much functionality that I'm not aware of -- I constantly need to Google or ask others about existing features. Also, although they are all under the Atlassian umbrella, I find it difficult to switch between JIRA Software and Confluence.
I have not used the technical support from Atlassian. In terms of online help and resources, they are a bit limited thus making it more of a challenge to troubleshoot issues and learn more functionality. There aren't a lot of resources available on the Atlassian site besides developer documents. It would be nice to have a blog or forum where users can get the help they need.
Our JIRA support is handled internally by members of our Product Support team. It is not supported by a 3rd party. Our internal support will always sent out notifications for downtime which is usually done on the weekend unless it is required to fix a bug/issue that is affecting the entire company. Downtime is typically 3-4 hours and then once the maintenance is complete, another broadcast email is sent out informing the user community that the system is now available for use.
One of their strong points i stheir documentation. Almost all of the basic set up needed within JIRA is available online through atlassian and its easy to find and very precise. The more critical issues need to be addressed as well and hence the rating of 8 instead of a 9.
Take your time implementing Jira. Make sure you understand how you want to handle your projects and workflows. Investing more time in the implementation can pay off in a long run. It basically took us 5 days to define and implement correctly, but that meant smooth sailing later on.
When I evaluated Spiceworks, it was not going to be replacing any ticketing systems. However, I did evaluate it and was not extremely impressed by the short demo I did. JIRA was selected because a branch of our company was already using it, so it made sense to consolidate into one service desk solution, and JIRA was the better option since it was less expensive and geared towards being a ticketing system.
Jira Software has more integrations and has more features than many of its competitors. While some of its competitors do have better UI/UX than Jira Software, they have improved this greatly over time. Atlassian also acquired Trello years ago, so that adds better user interfaces to the system. They do also offer a pretty in-depth library of how to customize the platform that others don't.