Aha! Roadmaps is used to set strategy, prioritize features, and share visual plans. It includes Aha! Ideas Essentials for crowdsourcing feedback. For an integrated product development approach, Aha! Roadmaps and Aha! Develop can be used together. The software is available with a 30-day trial.
$59
per month per user
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…
It is great for organizations that want to ensure that the work they focus on is the work that will have the most impact on value and drive them toward their strategic objectives. I consider it to be a real Product Management tool. If all you are looking for is a tool to hold your product backlog or collect customer feedback, then Aha! is probably going to be overkill for your needs
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
Aha! is an all around product management suite. It is great for breaking product plans into initiatives, features, and user stories. This helps the organization understand the product plan and what is driving individual work items. Unlike Jira and project management tools, it helps you prioritize by major themes, features, and releases. Once you start to use it, you can't go back to a project management tool because the views for organizing and prioritizing features just isn't there.
Aha! also excels at idea management. You can create a portal for users to submit ideas and manage them through a workflow. Users can submit ideas through a variety of channels, including email, ZenDesk, and SalesForce. You can even attach account values to an idea submitted through SalesForce, though the UI in SalesForce is a little kludgy. This is a great feature for those that have the capacity to manage feedback this way, but be aware that it takes time to manage.
Aha! works pretty well with Jira so that project managers can have their backlog that is understandable to the business and engineering can break down those work items however they want.
Aha! also has a lot of useful integrations: Slack, ZenDesk, Zapier, etc. It also integrates with every major software project management tool on the market: Jira, Pivotal, Rally, Redmine, and TFS.
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.
If you have the time and resources there really isn't anything you can't get Aha! to do for you in regards to managing workflow and releases. The Prioritization features are top of its class, the dashboards are getting better and better every day and the team all seem to really enjoy using it to manage their workloads.
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.
When we signed up for Aha!, we were assigned an Aha! team members to help us with training/questions. The meeting was set weekly, and it exponentially helped with our familiarity with Aha! Support is beneficial and has a lot of experience working with product teams.
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.
In terms of outright features, a lot of roadmapping tools have the same feature set. We chose Aha! based on look-and-feel, the easy learning curve, and the reviews it has. Between collaboration, milestone tracking, comment threads, and content importing and exporting, we had every feature in Aha! that we were looking for.
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.
It has helped us improve our product lifecycle communication. We have less wasted time spent figuring out where the project is and what it's waiting on. This has helped departments further down the project better use their time so they're already aligned with what's happening rather than waiting for a handoff.
Aha! has helped include our customers more in our product planning and especially in our bug fixes and new feature roadmaps.
Aha! has improved our strategy meetings or roundup discussions by storing everything in one place. They're shorter and more focused.
