Search results: Integrations

The intended use of GH integration is the following: Create features in Aha Push to GitHub as a handover of control to engineering Updates in GitHub trigger status changed in Aha This is a good start. If control is passed to engineering to manag...

As product owners use Aha as the primary repository to develop and track their roadmap, they want to enhance their planning phase by improving the existing configuration between Aha and Rally. Currently, capabilities, features, and user stories ar...

Our POs need to update user story summaries separately in Aha! and Confluence. If we had the ability to embed Confluence page info in Aha! and update the info from Aha! (push updates to Confluence) it would streamline information management. We us...

A previous idea of mine requests access for when Master Features are mapped as dependencies against Features, or vice versa. That one is a showstopper for my firm. However, it turns out that linking, say, an Idea against a Feature is also inaccess...

Add Dependencies and a mappable field from Rally

Dependencies (and other relationships) between Features, Epics are important in VSTS for developer info. As far as I can see, 'related items' integration exists for JIRA but not VSTS?

In some cases depending on workflow stories created in JIRA prior to an Epic being linked in Aha do not flow to the aha record. In this case we would like to have an option to not only resend the epic record values but also all the linked records.

Given that I have an epic in Jira, linked to a Master Feature in Aha And the Master Feature is found in "Release X", When I create a story beneath that epic in Jira, Then the story should be imported as a child to the Master Feature, AND assume ...

We use sub-tasks or even regular tickets in JIRA to do our estimates so they can be planned into sprints. When these estimate tickets are closed on the JIRA side it seems that the estimates they are for are zeroed out on the Aha side. The only thi...