ADD A NEW IDEA

Integrations

Showing 946

Support the ability to change a Jira project key

Aha! needs the ability to support changing a Jira project key. Occasionally teams change their focus and the Jira project name and key need to be changed to reflect that so Aha! needs to be able to support that as well.
Wayland Fox over 3 years ago in Jira 0 Future consideration

Merge on CSV import

What is the challenge? Multiple imports can cause duplicate entries What is the impact? Deleting duplicate entries is painfully slow since i could not find a bulk operation in Features list view Describe your idea Merge entries on import. Have use...
Guest 3 months ago in Integrations 0 Future consideration

CSV import is frustratingly archaic

What is the challenge? importing data is slow and tedious What is the impact? customers will get frustrated and abandon Aha Describe your idea The import process should be improved and use a little bit of AI to better match existing fields with cu...
Guest 3 months ago in Integrations 0 Future consideration

Option to enable "bypassRules" for Azure DevOps integrations

What is the challenge? ADO projects can have work items rules in place that prevent the Aha integration from working. For example, the ADO state transitions may be restricted by values in other fields. What is the impact? In order to prevent the r...
David I. 3 months ago in Azure DevOps Services and Server 0 Future consideration

Slack support for portal comments

What is the challenge? Our team works primarily from slack so the more functionality provided within Slack without use of other tools is key for adoption. What is the impact? Describe your idea In this case, we have a slack channel set up to alert...
Keith Davenport 3 months ago in Slack 0 Future consideration

Map VSTS/TFS picklist custom fields to Aha! choice list fields

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

Keep features in sync when they cross areas in Azure DevOps

This is useful when you have your DevOps areas configured by team. Once the features are pushed from Aha! to DevOps and evaluated by the team they need to be moved into the area for the appropriate team. Any team can work on any feature based on a...
Deb Gay over 5 years ago in Azure DevOps Services and Server 0 Future consideration

Allow mapping to the Rally iteration field

There is a built-in Rally field named iteration. It would be useful in many situations to map the iteration field to an Aha! field.
Austin Merritt over 2 years ago in Rally 3 Future consideration

Slack message when Idea is Created

What is the challenge? In Slack 2.0 integration there's no "Idea Created" option to send the idea to Slack when the user is creating idea. What is the impact? Large Describe your idea When configuring Slack message via the integration, please add ...
Shay Sagzan 3 months ago in Slack 0 Already exists

View in Aha! the author of a comment created in Azure DevOps

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...
Guest over 3 years ago in Integrations 1 Future consideration