The BMC Helix Configuration Management Database (CMDB, formerly known as Atrium CMDB) is a configuration management database.
N/A
Jira Service Management
Score 7.9 out of 10
N/A
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…
Track and manage hardware, software, and cloud service configuration and relationship. Measure the success of your configuration management process and policy with predefined KPIs. Automatically populate and update CMBD minutes with BCM Helix Discovery, BMC Helix Client Management, and other connectors. Import and federate data from other sources with powerful Integra tools using a rich set of API.
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
Some of the built-in functions and workflows are surprisingly limited given the fact that you can customize a lot with JQL. These limited areas do not allow you to use JQL. For instance, the built-in notifications are lacking. They have one that is great-- "notify on critical ticket creation"-- EXCEPT that it does not allow you to notify a group or anything, only individual users.
The ticket interface is a little odd for agents. Changing the status is not a simple drop down from unassigned to open to in progress to pending, etc. There are a couple of tabs ("investigate", "pending", "workflow") where you can change the status in different ways. Maybe I am just not used to this way of doing it, but I feel like it could be simplified.
It can get complicated deleting/changing some of the out-of-the-box fields and rules, because you never know what will break workflows or other automated/built-in features.
Once you have an understanding of the many use cases that this software can meet, you will be able to tightly integrate this into a ticketing system which increases the ROI of the product tremendously.
I have given this rating because, in my opinion, I don't see any downsides of Jira until now. We can customise workflows based on the project needs, including task workflows. Jira is very extensible, which is one of its most important features.
I gave JIRA a 9 rating since for me JIRA works according to its purpose. Since there is a customer portal, our clients can leave a comment or communicate with us using the PR ticket that way it is easier for us to also request any additional information we need for our investigation.
Let's detect potential conflicts when multiple changes are scheduled for the same time. Understand what services are affected by the ticket you're working on. Automatically route tickets to the potential solver based on CMDB data. Retrieve detailed configuration data for the assets you are troubleshooting. Resolve tickets faster. It is highly scalable.
We chose Jira Service Management due to its easy integrations with the rest of the Atlassian tools, as we have also invested in those. For the price, the ability to add or remove agents, and the cost being reflected in that, it was an excellent medium for us. For the foreseeable future, I do not see us moving off this platform.
