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

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

• 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

• 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

• 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

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.

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

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

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

• 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

• 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