Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 323

Filter on JIRA ID / JIRA Key attribute in Reports

The JIRA ID and JIRA Key are reportable attributes within Aha! but they currently cannot be filtered in the reports. Sometimes where a JIRA ID or Key are known, it would be useful to filter/search Aha! to find this information.
Guest almost 7 years ago in Integrations / Reports 10 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

Support the Salesforce Lightning interface

Currently the Aha! to Salesforce integration must be installed using the classic interface. After that, it can be used via the Lightning interface. As a Salesforce admin, it would be nice to be able to install the app via the Lightning interface a...
Scott Goldblatt about 8 years ago in Salesforce 15 Shipped

Configurable unit of time for Estimation field

We're using Aha with Azure DevOps integration. We’ve mapped the Estimate field in Aha with an estimate field in Azure DevOps. Our estimation process is basically as follows: * Product Manager creates Feature in Aha * Product Manager send RFC...
Guest almost 6 years ago in Azure DevOps Services and Server  / Capacity planning 14 Shipped

Add support for Jira "Parent Link" field

Jira Portfolio adds the Parent Link custom field to Jira. Aha! should support mapping this custom field so that the link between a feature and an initiative in Aha! can be reflected into Jira. This field has the custom field type of "com.atlassian...
Chris Waters about 6 years ago in Jira 14 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

Ability to customize Slack notifications

It should be possible to choose only few types of messages which should be sent to Slack (via Slack integrations). Right now every action in Aha! is creating a notification, it creates a lot of noise.
Guest about 10 years ago in Slack 17 Shipped

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

Allow features to be linked to existing Rally User Stories

If we already have User Stories in Rally that are duplicates of features in Aha! we want to be able to manually create a link between them.
Scott Goldblatt almost 9 years ago in Rally 10 Shipped