BMC Track-It! vs. Jira Service Management

Track-It! is great for a small-to-medium sized enterprise that has a fairly small IT department but needs far more control of tickets than just email and spreadsheets. It scales well enough as IT departments grow, adding techs is simple enough, as is changing the workflow. A large company would probably be better off with a different solution. The lack of easy customization, and the shortcomings it has in workflow templates (which would be a nightmare for project management) means it won't scale up that far.

Incentivized

I think using a ticketing system is very easy to use and allows multiple teams to create help desks in the same portal. In terms of internal usage, I think this is a great option. However, suppose you're trying to keep internal items and external helpdesks in the same instance. In that case, this is not ideal, as there is no effective way to separate the two instances to protect internal data better.

Incentivized

• The software is simple to use. There doesn't seem to be a lot of bells and whistles which could be attractive to some users.
• It includes email notifications where users are able to respond to an email and it updates the ticket.
• The system gives you the ability to customize your view so that you only need to see that tickets that are relevant to you or your group.

Incentivized

• Integration with many of the most common tools companies are using (Slack, MS Teams, Salesforce, ... etc)
• Natural workflow with Jira (as product development / project management tool) which makes the full fix and follow up of the tickets / issues very easy to follow
• Allow multiple different entry points and work flows for as many different needs your teams / company have

• Configuration is convoluted in my opinion. Getting the email to flow how you'd like is difficult.
• A lot of the configuration option names aren't very clear. It seems they use their own terminology for things I would have never guessed.
• Support is lacking - asking them for help always results in them directing you to a KB article. Sometimes you just want hand holding.

Incentivized

• Navigating through issues outside of a kan ban board can be confusing and task heavy.
• It's easy to clutter up the tool. It could use some easy clean up capabilities.
• User interface is decent, but could use work to make it more intuitive.

Incentivized

If you're used to other tools in the Atlassian ecosystem, you'll feel right at home with JSM. It's also a platform that technical folk can easily pick up. However, I wouldn't recommend using JSM as a company's first jumping off point into Atlassian. There are a lot of other 'newer' tools that provide sleeker ITSM systems at a similar cost.

Incentivized

We have rarely needed to use Support for BMC Track-It!, but in the times that we did need to use it, they were excellent. The biggest issue is that after not paying for support for about three years, now that we NEED support, it is too expensive for us to receive. This is due to the way their support is billed. So long as you never drop support, then you should be fine.

Incentivized

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.

BMC Track-It! is much more bare bones compared to ServiceNow products, and if your department has the money, ServiceNow is a much better option. Not only is the Knowledge Base much easier to create and publish articles, but the asset management in BMC Track-It! is practically useless. BMC Track-It! is more cost effective, and with a small amount of technicians there's likely no reason to need a bigger solution, but it leaves a lot wanting.

Incentivized

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 drawback of this is the price is significantly more expensive rather than hosting it yourself. Zendesk does have some additional features such as commenting on multiple tickets at once that JSD does lack. However, switching to JSD was significantly more cost effective because we have the ability and the infrastructure to host our own ticketing system, something that Zendesk could not provide. Ultimatley switching to JSD saved us money and allows the ability for integration with all of the other Atlassian Suite products that we use on a day to day basis.

Incentivized

• The biggest positive impact it had on ROI was that the software itself didn't require any expensive ongoing maintenance contracts since it was installed and managed by our organization.
• The negative aspect of this is if there was a major problem with the software, then it would require contacting the vendor, at which point it could become expensive for a service call.

Incentivized

• It is definitely cheaper than Salesforce
• It allows the IT service desk to be more organized and respond more quickly to tickets, which can save time for both agent and requester.
• Some things are "not quite there" developmentally, so this means that internal IT will need to spend more time developing and testing the product.

Incentivized