Adding another feature request to gain visibility again to this needed enhancement. Our features board contains a combination of in-progress, scheduled and further out tentative / aspirational releases. We continually forget to change the release ...

Sometimes, an idea is submitted to a portal that is mapped to a different workspace than the one that needs to respond. When moving the idea to the correct workspace, the link to the original submission is no longer valid and the submitting user e...

While I recognise that moving JIRA issues between projects breaks the AHA integration links, the workarounds proposed here are not helpful. Option 1 ("Relink each record manually") is the only viable workaround, with options 2 and 3 being too haza...

When a feature is created from a work request of an idea/epic, the features should be automatically linked to the epic (it is created as a related record, but we need the manually link the feature). The link should be be automatically created so d...

The Releases Settings dropdown on Releases > Gantt includes two options: Show/Hide Shipped releases Show/Hide Parking lots Showing/Hiding shipped releases makes sense since a shipped release is date-bound, so a Gantt view can display it. But...

What is the challenge? The Jira integration does not currently support the table markdown syntax What is the impact? The result is a formatting issues when a record including a table within the description is synced to Aha! via the integra...

What is the challenge? We often know we will have work in future releases which are reliant on other teams to define or which we want to plan to leave space to work on but we don't yet have all the information. We currently write [Placeholder] in ...

Handling of duplicate ideas has been a very tricky thing. The way we solve this is by promoting multiple ideas to the same feature, making the feature a kind of 'control point' where all of the ideas come together. The problem is that this introdu...

What is the challenge? Currently, the Team fields do not display on Requirement records if the parent Feature is a Develop/Teamwork Parking Lot feature; however it does display on the Feature's Requirements if the record is assigned to the Team ...

Hi team!Automation rules help us assign to-dos for our launch readiness process. This works great for tracking work, however, it's a challenge to ensure each workspace has rules in place and that these rules are the same. We would love the ability...