Integrations

Right now we have an integration set up between Jira and Aha (which is extremely useful). However, whenever a feature in Aha that's linked to an issue in Jira has its release updated (e.g. moved from "v1.12.0" to "Backlog"), if the release to whic...

For those who are using Azure to track application usage and performance it would be useful to have an integration that could display the feature usage metrics from Application Insights similarly to the Google Analytics integration.

Who would benefit? Customers with multiple integrations set up to ADO who are wanting to move features to different Epics as their plans change. What impact would it make? How should it work? The parent/child relationship should be tracked across ...

Who would benefit? anyone using the integration with aha and GitLab What impact would it make? improves resiliency and stability of the integration How should it work? Currently, to set up the GitLab integration a user in GitLab must use a persona...

As the service hooks from DevOps to Aha are seldomly failing, it often results in having some records not in sync in Aha. This can be solved by running an update of all the linked records from the Aha integration page, but this requires to be manu...

Normally our product managers works on Initiatives in Aha! by editing/ranking them. Those field changes and ranking will sync to Jira backlog for architect team to work on follow priority of Initiatives. When a rank is changed for a record in Aha!...

Escalating this issue again here as it's now been moved to Atlassian's Long-Term Backlog & is critical to the adoption of Aha! at my company (as in people want us to go back to just JIRA bc syncing is so bad & data is out of date).  U...

Currently Rally import functionality shows only top 10 records extracted for the set criteria. Want the ability to see all the records with checkbox to allow 'pick & choose' for import Do not show the records which were already imported or linked

It would benefit users who are trying to clean up a project that already exists. There may be information captured in pivotal that would be time-consuming to replicate.

I don't see a way to connect Aha's "native" record hierarchy to a similar hierarchy in Jira. Using epic --> feature as an example, if I select the parent epic while editing a feature, that creates a "Belongs to epic" relationship under that fea...