Share your product feedback

ADD A NEW IDEA

Integrations

Showing 949

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

Keeping link to Jira when disable an integration

When we disable an integration to Jira, we mean it to be we have a new Jira project to integrate to. It makes it easier on the integration on the feature to not have a huge list of Jira projects to integrate to and only to the projects that are ac...
Carina Velazquez about 1 year ago in Integrations 2 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

Webhook for integration log errors

I'd like an option to create a webhook that will send me messages when integration errors occur. I will use this webhook to create messages in Teams, so I know that I should go to either Aha or the source system to fix the issue.
David I. 3 months ago in Integrations 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

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

If comment is deleted in Jira, add a tag <Deleted> to Aha to ensure users are aware of the change (& Vice versa)

What is the challenge? currently, comments that are deleted on one platform, do not get deleted on the other platform (& Vice Versa) What is the impact? Users who work dedicatedly on Aha (like Top Management) will continue to view out-dated co...
Maria V 3 months ago in Features / Jira 0 Future consideration

Allow for parent-child linking across Jira projects without using an integration template

Some organizations that use SAFe store high-level records in one Jira project and the tactical work in team-specific Jira projects. These are often integrated to the same Aha! workspace. Today, you have to use the same integration template in the ...
Emily Yankush over 1 year ago in Jira 0 Future consideration

Integration with Airtable

We're going to start using Aha! on our product team, and we use Airtable for our dev tasks -- would be great to have the ability to connect items in here with tasks/projects/epics in Airtable.
Guest almost 6 years ago in Wanted 5 Future consideration
Idea management by Aha!
Create your own ideas portal to crowdsource feedback
© 2024 Aha! Labs Inc.•All rights reserved