Absolutely and on both ends - Both Atlassian and Aha! recommend layering Aha!'s roadmapping and product management stuff over a developer's Jira.
Aha! has Jira integration off the shelf, and there's https://marketplace.atlassian.com/apps/1211698/aha-roadmaps-for-jira?hosting=cloud&tab=overview on top of that to provide even more.
However. I'm looking at the development and business project types.
Service Management is a little different, it's tracking calls and requests, which are unlikely to have much to do with design (if it's product design stuff, I'd be using Aha! to capture that), and even less to do with development. Ok, you may well log a bug in a service desk and that leads to development work to get it fixed, but that's not product design or development, it's maintenance and fix.
I'd say that while there's a lot to be had from wiring the two together, you'll need to have a think about what "customers" see. In a Jira service desk, customers only work with "requests". Aha! <> Jira integrations tend to work mostly with "issues". There is an issue behind a request, but Aha won't be looking at what the customer sees (requests), it'll be seeing what your service desk agents see (issues)
That may need a bit of thought, but it won't stop the two of them working well together.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.