BMC FootPrints is an IT service management (ITSM) solution featuring workload automation.
N/A
Jira Service Management
Score 8.0 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…
BMC Footprints is so well suited to keep the documentation easy to read and find, as same as typification. You can find specific documentation for an audit so fast and export a report using the specific criteria that you need to comply with your boss or audit needs. As I told before, BMC footprints need to be more friendly to the end users because they get lost many times trying to track some ticket or typing documentation.
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
Documentation. We try to reduce the amount of paperwork needed for staff to do their job, so by automating certain tasks, we are able to speed up the resolution process for trouble tickets.
Reporting. We'll use the reporting tool to get the number of tickets opened, response times and can go into granular reports.
Surveys. When tickets are closed, we automatically send out surveys to end users to get valuable feedback on how we did and what we can improve.
Purpose based configuration- It would be beneficial to see a more purposed based, out of the box, configuration option. For example, if you need PCI compliance, more intuitive reporting would make managing compliance much easier.
Initial design and implementation- Don't think that your experience as an IT professional will allow you to stand this system up on your own. To properly configure Footprints and set yourself up for success down the road, get Professional Services with this one.
Somewhat behind the times- Service Core is making a huge leap forward with the latest version, 12, but Asset Core is far behind. There are quite a few quirks to how the application works and how it is used.
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.
It has been the business decision to go with them and that is what we will do. Going back, this would have not been the choice, but nothing can be done about it now. We are stuck with this application for years to come. Wish there were other possibilities that could be done.
It's so simple to use and customize however you want. You can create new workspaces and workflows with ease, set up new users, incoming email rules, customize the layout of the forms, and even change the colors and logos. It's just very easily customizable overall. It's also really straightforward to figure out how to use, you really almost don't have to show somebody how to use it. If you just sit them down in front of it and let them look it over, they could figure it out themselves easily.
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.
I've had no issues with the support for FootPrints. We haven't really had to use them all that much over the years, but when needed they have always been prompt and knowledgeable at dealing with any issue. I've worked with a lot of different support teams over the years, and they have been one of my favorites to work with.
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.
I was not involved in the selection process but in my opinion either SQL or Access databases would have worked just as well without the same amount of cost. These two systems would have been much easier to manage and would have tracked the same information in a less convoluted process and expense.
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.
