Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Does a connector from Jira Service Management to Aha! exist

Have Atlassian wired up any automation between a Jira Service Management project and Aha.io for feature request tracking and Aha updates showing the status of the Aha item and potentially from there for Aha to link to the Jira Dev project if the requested feature is approved for a scrum team backlog?

1 answer

0 votes

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.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

312 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you