Ability to create and manage ServiceNow epics through Aha! Product Management would define the epics and they would flow down into ServiceNow
New ServiceNow integration
Automatically send requests captured in ServiceNow to Aha! software as ideas — integrating internal feedback into your planning process. This new integration, built by ServiceNow, is fully customizable.
ServiceNow provides triggers and actions built around the Aha! API — and an easy-to-use flow designer — so you can chart the perfect workflow for your team. You can even use webhooks to make the integration bi-directional. This ensures that updates flow smoothly between tools and data is always in sync. The integration also supports the Aha! APIs for other record types, like features, releases, and more — so you can build your ideal workflow across the two systems.
would be most beneficial to our organization as customer requests initiate in ServiceNow and we manually recreate in Aha Ideas or Directly as a Feature.
Like many others have said we'd like to submit Ideas from ServiceNow that we can progress.
It will also be ideal for our ServiceDesk to escalate bugs into Aha! for scheduling etc.
We would like to send work items to Aha to eliminate duplicate data entry or import/exporting manually
I would like to see ServiceNow tasks become Ideas on our Aha board.
All our planning of the upcoming projects is happening in ServiceNow and we need a 360 view of the road maps across all the business units via Aha. So we don't want to have double entry of the existing projects as well we don't want to have to use excel as intermediate
Also updating Aha epics/features from ServiceNow epics
We don't like sending our users to a lot of different systems, so would like to use ServiceNow for intake of ideas and pass that idea to Aha when it's ready to leave the ServiceNow ecosystem. bi-directional integration that provides updates back to the ServiceNow idea as the idea progresses in Aha would be nice-to-have. ServiceNow and Jira do a good job of integrating the different Jira objects with the ServiceNow objects. Would be great if Aha could do the same thing
Concur with the request for integration with Ideas. We don't want to drive our user community from the self-help ecosystem we have in ServiceNow.
We use Aha for Product Strategy and planning. ITBM is used for many workflows in our organisation, particularly incidents and problems, and also Project Management.
Our key use would be sending Epics from Aha to ITBM as Projects.
We leverage Service Now heavily for project and task intake. Would like a Service Now integration to bring these requests into Epics + Features. Not sure if it would make sense for them to flow through Ideas but that could be an approach.
I would like the ability to submit Ideas to the Ideas Portal, from ServiceNow. Similar to the Salesforce Ideas integration, where you can submit an Idea from Salesforce, without actually visiting the Ideas Portal itself.
I would like the ability to bring in incidents, problems, etc. from ServiceNow to incorporate into epics and features.
Adding my vote here as well. I'd love to see a way to integrate epics in AHA to Requests in SNOW, and stories to C Tasks maybe. I'm not sure if my company is gonna buy SNOW PPM or not, and if not, I think AHA + SNOW would be a great combination.
This would be a real need. where are we with this?
What I REALLY need is for ServiceNow tickets to be able to create a record (unsure if idea, epic, or what) in Aha. Scenario, support team identifies that a ServiceNow ticket is actually an enhancement request, so needs to come to Product Management / Aha to be considered for the roadmap.
Would help provide the end-to-end product lifecycle.
amen, really need this
We currently use both and have Aha set up with Strategic Initiatives then Epics then Features - once we are ready for development it basically gets copied into service now and translated down to the user story level.... would be extremely helpful to have some integration.
Our company is looking for the same! We don't want our customes to maintain yet another log in to another system when the blast radius between Aha and Service Now is identical!
Adding my vote to this.