Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 913

Configurable destination of imported features

As a product manager, I should have control over the destination of where imported features and epics go so that they are in the release or parking lot where they belong. Today, the destination of imported items seems almost up to chance although ...
Tom Beck about 6 years ago in Azure DevOps Services and Server 9 Future consideration

Allow attachments to Feature comments to be integrated to Azure DevOps

When you add comments to a Feature, and you have integration with Azure DevOps (ADO) configured, you can have these comments passed back and forth. Unfortunately if you attach a file to a comment it will not get passed between Aha and ADO. When yo...
Guest over 3 years ago in Azure DevOps Services and Server 0 Future consideration

Integrate with Invision

I’m not sure if Invision supports an API yet, but it would be an ideal integration for Aha. Right now, I think Aha does a great job of what I would call the front end of the funnel for product management: capturing ideas, managing a backlog, high ...
Chris Waters over 9 years ago in Wanted 18 Future consideration

Integrate with ClickUp

Allow users to push information from Aha! into ClickUp and vice versa. A product roadmap/plan from Aha! could ideally be plugged directly into tasks in ClickUp. A project manager would then create their roadmaps in Aha! while the team works in th...
Guest over 6 years ago in Integrations 8 Unlikely to implement

Customize fields in the Slack integration

Who would benefit? Internal stakeholders giving feedback to product teams What impact would it make? Reduce overhead in editing ideas once they have been pushed to Aha through the Slack integration How should it work? When creating an idea using t...
Guest 3 months ago in Slack 0 Likely to implement

Sync the change of parent link made in Aha! across 2 Azure DevOps integrations

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 ...
Stuart Blair about 1 month ago in Azure DevOps Services and Server 0 Future consideration

Move Aha! Requirements when linked JIRA Stories are Moved to a different Epic/Feature

The specific use case that this commonly occurs for is the following mapping: Feature = Epic and Requirement = Story; however, the same would apply to other mappings parent child mappings such as Story/Sub-task as well. Current behavior: The i...
Matt Case almost 8 years ago in Jira 13 Future consideration

Defect: Jira Integration record mapping doesn't use custom terminology

Who would benefit? Anyone with custom names for "Epic" or "Feature" who is setting up a Jira integration. What impact would it make? Prevent failure of the integration (which took us several hours to figure out). This was particularly egregious fo...
Guest about 1 month ago in Jira 0 Future consideration

Allow project access token to be used instead of personal token for GitLab integration

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...
Guest about 1 month ago in Integrations 0 Future consideration

Iteration to Release not Retaining Parent Relationship with other Records (AzDo Integration)

Who would benefit? Aha users What impact would it make? Elimination of lost records (Azdo integration) How should it work? When using iteration to release, the integration would look at the area path of that record as well as the iteration path. S...
Guest about 2 months ago in Integrations 0 Future consideration