Coremetrics / IBM Digital Analytics (discontinued) vs. Jira Service Management

IBM analytics has continued to improve upon the days of being the original core metrics. After using the updated version for quite some time, it has been great at providing the needed analytics to measure ROI and goal performance for our quarterly KPI's. It has resulted in a great increase in web engagements although we are a midsize company, smaller outfits may not need such an expensive option.

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

• IBM CXA comprises an acquisition called Tealeaf. This tool has deep heritage and this is evident in its present-day capabilities.
• The Universal Behaviour Exchange or UBX puts the concept of personalisation at the forefront. The ability to combine physical (analog) and digital transactions to create the complete picture of a customer journey, is a stand out benefit.
• The solution does not have to involve the purchase of software. IBM CXA can be sold as a service bundled with analytics as a service. This not only lowers the cost of ownership, it gets around one of the principal issues. Strong staff with design and analytical capability to drive the solution and deliver tangible benefits.
• The seamless integration of Watson AI services to help with the heavy lifiting. Watson reinforces the analytical focus this solution has and can learn to recognise situations specific to a company.

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

• The user interface is in Flash, which can be very frustrating and slow at times. Apparently, this is to be transitioned in a future release.
• Can only segment the last 93 days of data. Any historical segmentation beyond the 93 days must be run in Explore (which is credit based, and has its own limitations with the number of credits per month, based on the initial contract with IBM).
• Reports can only display 93 days of data at a given time for custom date ranges. There are pre-programmed date ranges setup with IBM during implementation (last week, last month, last quarter etc.), but are not flexible enough to answer more specific questions.
• Certain reports cannot have segments applied, making answering some simple questions a bit more tricky. For example, I can create a segment around mobile devices and apply it to the marketing channels report, but I can't create a marketing channel segment and apply it to the mobile reports.
• Built in API calls allows for nice report design and automation.

• 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

IBM Digital Analytics is a great solution for our clients and I believe they offer the best solution for the retail space. We have access to IBM support via email or live chat and they can answer many of the reporting questions that come up. IBM is receptive to our feedback of the product so I am confident they will continue making improvements

Very easy to implement and use.

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.

Never had any issues

As reports are templated, the system is pretty quick. Sometimes you have to wait a bit for a report to render. Or you might have to re-load the page. But there is no real issue here and the system is on par with other similar systems.

Overall, the level of support is very good and I would say it is a strong asset of the solution. However, you can sometimes feel that there is a difference of level among the support team.

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

Online training is really great. One of the best assets that they have. Lots of great videos, pop quizzes at the end of each module. Fantastic. Other tools have similar features, but not as good.

See previous comment: reading and understanding the encyclopedic implementation guide is a must.

Much of the work we did in IBM Digital Analytics could have been answered through Google Analytics, a much simpler, agile and FREE solution set. Not mention, given the vast number of Google Analytics USERS, free and actionable support is simply a click away ... this compared to IBM Digital Analytics fractured and often absent support service.

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

This solution can support large amount of data and transaction. The way that user management features are built, it shows it is meant for large organizations.

• We spend too much time trying to work around bugs on the new UI.
• We spend too much time trying to figure out how to make certain segments work because support and the knowledge center are lackluster.
• Our sales rep is very unresponsive and leaves us searching for a lot of answers on our own, including what other products we may benefit from that IBM offers.

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