Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 323

Integrations 2.0: Auto accept import records

We would like the ability to have new records created in JIRA/Rally automatically import into Aha! Currently, they have to be accepted in Aha! prior to import. This causes an extra step in our workflow we do not wish to have to go through each time.
Danny Archer about 7 years ago in Integrations 7 Shipped

Link existing GitHub issues with a new Aha! Feature

The current Aha! - GitHub integration lets you sync features to GitHub issues. This won't work in the opposite way. However, It'd be nice to have an editable field to reflect that the Aha! feature is linked to a GitHub issue.
Guest over 9 years ago in GitHub 14 Shipped

Map Jira's "Won't Fix" resolution status to Aha!s "Won't implement" status

When the Jira workflow is set up to "Close" a ticket with the resolution status of "won't fix," there currently is now way to map that against the Aha workflow. It would be great to also access the Resolution status from Jira to handle this case.
Guest over 9 years ago in Jira 17 Shipped

Jira Integrations 2.0 support for time tracking

Support synching the work logged from JIRA to Aha! in 2.0
Deleted User about 7 years ago in Integrations 11 Shipped

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 7 years ago in Azure DevOps Services and Server 9 Shipped

Enhance two-way sync with Rally to support Rally -> Aha!

Features are created in Aha! and then pushed to Rally. User Stories (US) are created in Rally and associated to the Features. These associated User Stories should be synced back to Aha! and associated with their respective Features as Requirements
Guest almost 9 years ago in Rally 15 Shipped

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 int...
Matt Case over 8 years ago in Jira 13 Shipped

Allow all customers to add 1.0 Slack integrations until the 2.0 Slack app is approved

What is the challenge? My infosec policy prevents me from being able to add the 2.0 Slack integration because it's not yet approved by Slack However, I'm unable to add 1.0 integrations to new workspaces. What is the impact? I can't use the Slack i...
Nathaniel Collum 5 months ago in Slack 0 Shipped

Ability to map standard fields in Aha to custom fields in JIRA

It would be really useful if I could map standard fields in Aha to custom fields in JIRA. For example... - Assigned User to Product Owner - Aha Score to Business Value These are fields that we use in JIRA that we are having to manually type in aga...
Guest over 10 years ago in Jira 10 Shipped

Warn when there are incomplete Jira webhook settings

When setting up a webhook in Jira, you can choose specific events to trigger the webhook event. Some users accidentally select "Exclude body" which results in empty webhooks returning to Aha! and no updates being made. Other users create the webho...
Madeleine Black over 2 years ago in Jira 1 Shipped