My ideas: Knowledge bases

Part of our research ops process includes live, in-person, sessions with single and multiple users which we record and have transcribed. However, bringing those conversations into an Aha! Empathy Session is a BIG pain in that we have to copy/paste...

Empathy sessions are really cool - but in practice I have found that it would be great if we could do the meeting over video, and then have the transcription generate the current text-based empathy session interface. Each comment could have a time...

The desired use case to see supported is as follows: 1. Director of User Experience or Product Management creates (at the product line level) all possible personas for a product line.2. Each Product Owner then removes/hides (at the product level) ...

What is the challenge? I have to attempt many times to drag items into the list. What is the impact? Describe your idea Fix this UI bug preventing the user to drag over an item or provide a new way to add items from the left panel in...

Github integration messages in comments is great for smaller stories, but for anything non-trivial it becomes very easy to lose meaningful comments in the middle of a commit barrage. It would be very useful to have these either separated, or group...

I would like to be able to run reports to see: How many empathy sessions we have run and when Who was invited and attended The insights, learnings, and ideas that come out of the session Each of the messages sent We can use these report to share w...

Similar to the ability to create Ideas via email, we would love the ability to create Features via email submission. Our ideal workflow is to have support issues and bugs submitted into Aha! and this would simplify things so that users aren't send...

We are currently using the Aha.io and pivotal tracker integration to help seed our product roadmap into the engineering team's workflow. This has been great so far but the one biggest points of friction is trying to keep track of the features that...

When I delete a feature or a requirement in Aha!, I then have to go to Jira and delete the corresponding epic or story. Would love it if deleting a feature in Aha! deleted the linked epic in Jira and all stories for that epic. Likewise, deleting a...

Synchronisation of the owner field. Stories created in Pivotal Tracker should have the corresponding owner on the Pivotal Tracker side. That can be determined based on e-mail, your team confirmed that it is possible. Priority 2 of 4