ADD A NEW IDEA

Integrations

Showing 916

Add 2-way integration mapping for release start and end dates

Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release. Now that this date is set manually, it should be poss...
Austin Merritt about 4 years ago in Azure DevOps Services and Server  / Integrations / Jira / Rally 2 Future consideration

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

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

Create Aha! note from Slack message / thread

Who would benefit? everyone who uses slack and aha What impact would it make? reduce duplicated effort, improve knowledge management capture and record keeping How should it work? it should be possible to have a command to capture threads, slack c...
Guest about 2 months ago in Slack 0 Planning 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

Handle multiple FixVersions in JIRA

An Aha! feature can only be associated with a single release, however it is common for development teams to associate multiple fix versions with a issue in JIRA. Currently, the Aha! feature will overwrite the fix versions in JIRA if the fix v...
Danny Archer over 8 years ago in Jira 15 Future consideration

Complete Auto Import Functionality -- not just children of existing linked records

This is regarding the JIRA integration feature: Automatically Import New Records: Records will be imported automatically to Aha! from Jira. This applies to records which are created as children of previously linked initiatives, releases, mast...
Guest about 5 years ago in Jira 5 Future consideration