What is the challenge? Currently, there is no out-of-the-box way to easily identify which workspaces lack integrations. This makes it difficult for administrators and product owners to ensure all relevant workspaces are connected to necessary to...

What is the challenge? When using an integration template to connect Aha to Jira, the child integrations inherit the Jira project from the original template. This causes authentication issues if the user doesn’t have admin rights to that specifi...

VSTS/TFS picklist custom fields are treated as strings and cannot support option mappings. Mapping a picklist field to an Aha! choice list field should provide the option to click Configure and map the choices.

We're going to start using Aha! on our product team, and we use Airtable for our dev tasks -- would be great to have the ability to connect items in here with tasks/projects/epics in Airtable.

Currently, our main work in DevOps gets done within Task items which also have effort spent inside. These however are not a sync-option within the "To-Do" level of Aha!. The fields "Name, Description, Assigned to, Due Date (and maybe effort or oth...

In integrations with Azure DevOps, comments created in ADO show the integration name rather than the individual as the creator of the comment when looking at it in Aha!. This can cause confusion for Aha! users who can't easily understand the conte...

What is the challenge? As we do not use releases for some workspaces not everything pulls in automatically, so there are things in the integration updates tab that we don't know are there until we check it. What is the impact? Sometimes we...

What is the challenge? Confluence integration is only one way. It would be great to have the other direction (Confluence > Aha), so that we can pull into docs into our feature cards. What is the impact? We can only add a link to the PRD...

Currently the Github integration forces us to select a repository in order to integrate with a project but we have the need to integrate with projects that are not associated with repositories.

This request is to support the mapping of ADO boolean fields to Aha predefined droplist and tag fields. Currently, Azure DevOps Boolean fields (true/false) cannot be mapped to Aha fields. Rather, in ADO, you need to create a field as a picklist in...