ADD A NEW IDEA

FILTER BY CATEGORY

Integrations

Showing 849 of 8115

Provide a warning explaining consequences when changing the workflow used in a workspace

When a user moves to a new workflow in a workspace or team, there can be a loss of data related to the statuses like cycle time, time in status, etc. I would like to understand these consequences before making the change so I am not surprised with...
Max Robbins 4 months ago in Wanted 1 Will not implement

Support large volumes of repos in GitHub integration

My company has been migrating from GHE to GitHub.com, and the default repo permission is set to "internal". This is causing individual users to have access to over 15k repos. In Aha, this large number of repos is preventing users from being able t...
David I. 3 months ago in GitHub 0 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 12 months ago in Jira 1 Future consideration

MS Planner integration

In our department we have developer teams working with Jira but also other teams for e.g. process improvements, consultancy... It makes no sense to track their work in Jira as they only need a simple board for their needs. Currently they use the M...
Guest over 4 years ago in Wanted 7 Future consideration

Integration with smartsheet

Product implementation and execution schedule can be build up with much more detail in smartsheet. A combination of aha! and smartsheet can be a much more powerful tool for our customer.
Guest almost 8 years ago in Integrations 21 Unlikely to implement

Integration 2.0 for Gitlab

Gitlab is an important integration, but still not covered by the new 2.0 integrations
Fabio Brito almost 4 years ago in Integrations 8 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 almost 3 years ago in Azure DevOps Services and Server 0 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 over 5 years ago in Azure DevOps Services and Server 9 Future consideration

Include comments when importing from Jira

When you initially import issues from Jira the Jira comments are not included. This means I have to copy them across manually for every issue - very time consuming. (Comments added to Jira subsequently do appear in Aha.) Please can you include Jir...
Guest over 7 years ago in Jira 5 Future consideration

"Real" 2-way integration with pivotal

The pivotal integration only allows for 2-way integration only if originally pushed from aha initially. Even then it's pretty limited to status and description. If I create an 'feature' in aha which maps to an 'epic' in pivotal, and someone add...
Guest over 8 years ago in Pivotal Tracker 23 Future consideration