BMC Helix Remedyforce vs. Jira Service Management

[BMC Helix Remedyforce] is probably best suited for an MSP who needs to keep multiple clients separated. If you were an internal IT department I think the additional features it has would be lost. When dealing with an MSP who needs to know what software and what issues have effected specific clients it is very well suited to do that.

Incentivized

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

• An admin user is able to quickly create a request definition with all of its components from one screen. We use to have to go to the 7 or 8 different screens to create each piece of the request definition.
• Ability to update multiple Incidents/Service Requests at once with the update button. This allows essentially an inline edit functionality within Remedyforce.
• Change management schedule is a great feature as well to be able to see how changes align and what there expected start dates/times are.

• Manageable workflow to ensure all users follow the same process.
• Can ban boards for easy visual of ticket status.
• Very flexible tool that can adapt to lots of different uses outside of the traditional service desk model.
• Added communication tools help you get out of e-mail jail.

Incentivized

• The ability to monitor/regulate the volume of tickets when you integrate with your monitoring software. We have so many items that trigger alerts, creating a ticket for each is somewhat overwhelming. Would like to be able to better control when an incident should be created.
• Being able to report on Service requests and tasks together would be nice. Right now I have to do it separately as they are in different buckets, so to speak.
• Remedy console is an improvement from where it started but can still be a cleaner interface for a tech to be able to work out of for their day to day work.

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

Incentivized

The total amount of time spent from installation to configuration for a minimal ticketing system was 2 hours. Maintenance and customization for the application can be completed with a great amount of ease. In addition having a customer portal is an added benefit that pays for itself

Incentivized

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.

They care about your success.

Incentivized

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.

Incentivized

Learning industry best practices or gaining insight on them from either BMC or an implementation partner would have saved some headaches we faced after roll-out.

Incentivized

I previously worked with tools like Service Manager which were difficult to configure, administer and maintain. The support options were very limited. Remedyforce has local US support, dedicated reps, and a more developed infrastructure to work from to support an organization. This runs on the Salesforce platform so worrying about server failures and unscheduled outages was no longer going to be an issue for us. Self service, knowledge base, and change control were just a few highly utilized features that helped employees support themselves and automate very manual processes.

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.

Incentivized

• Remedyforce has allowed us to eliminate other solutions that provided similar features. By now using one true ITSM we have been able to save money which in higher education is always a concern.
• The reports and dashboards allow for a birds-eye view of our daily operations and provide managers and executives the information they need to make important cost saving decisions.

• JIRA has been incredibly useful. Our work is more organized and easier to view by the team members as well as upper-level people.
• Our work is correctly assigned and when there are issues, they can be immediately addressed within the tool.
• Users can attach screenshots or files of issues that help clarify the ticket. Developers can attach relevant data as well.

Incentivized