ADD A NEW IDEA

FILTER BY CATEGORY

Integrations

Showing 862 of 8300

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 almost 6 years ago in Azure DevOps Services and Server 9 Future consideration

Integration with MS project

It would be great to tie into MS project for the high level milestones and phases so as either is updated....it would update the connection.
Guest over 6 years ago in Wanted 10 Future consideration

Provide alternative way to match users when email address is not exposed in Jira

Some time ago, Atlassian made changes that requires users to share their email addresses on an individual user profile setting. When that option is not checked, Aha! is not able to view their email address and if assigned user is mapped, is not ab...
Madeleine Black about 1 year ago in Jira 1 Future consideration

Add better error handling for 'unhandled error exceptions'

When using AHA to integrate with other platforms such as Jira, sometimes fields are not mapped correctly due to either changes in Jira or custom fields in AHA. When this mismatch happens, we are only presented with 'unhandled error exception. Plea...
Guest 3 months ago in Jira 0 Future consideration

Notification when an integration is down

Would like to see some way of setting user(s) to be notified if there is an interruption in communication between integrated system.
Guest 4 months ago in Jira 1 Future consideration

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 over 3 years ago in Azure DevOps Services and Server  / Integrations / Jira / Rally 1 Future consideration

Make the standard tags field mappable for requirements

Both epics and features have the standard tags field mappable when setting up an integration. Requirements now have a standard tags field added to the record but it is not available in the mappings. It currently requires a custom field be created ...
Justin Waldorf over 1 year ago in Integrations 1 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 about 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 over 7 years ago in Jira 13 Future consideration