Skip to Main Content

Share your product feedback

ADD A NEW IDEA

Integrations

Showing 944

Sync the change of parent link made in Aha! across 2 Azure DevOps integrations

Who would benefit? Customers with multiple integrations set up to ADO who are wanting to move features to different Epics as their plans change. What impact would it make? How should it work? The parent/child relationship should be tracked across ...
Stuart Blair 10 months ago in Azure DevOps Services and Server 0 Future consideration

Defect: Jira Integration record mapping doesn't use custom terminology

Who would benefit? Anyone with custom names for "Epic" or "Feature" who is setting up a Jira integration. What impact would it make? Prevent failure of the integration (which took us several hours to figure out). This was particularly egregious fo...
Guest 10 months ago in Jira 0 Future consideration

Allow project access token to be used instead of personal token for GitLab integration

Who would benefit? anyone using the integration with aha and GitLab What impact would it make? improves resiliency and stability of the integration How should it work? Currently, to set up the GitLab integration a user in GitLab must use a persona...
Guest 10 months ago in Integrations 0 Future consideration

Iteration to Release not Retaining Parent Relationship with other Records (AzDo Integration)

Who would benefit? Aha users What impact would it make? Elimination of lost records (Azdo integration) How should it work? When using iteration to release, the integration would look at the area path of that record as well as the iteration path. S...
Guest 10 months ago in Integrations 0 Future consideration

Integration with Help Scout

Our customer success team uses Help Scout as their main support tool to assist our customers. It'd be nice if they could just take the feedback given by customers in their Help Scout ticket and send it directly into Aha! as an idea.
Jacob Papka over 2 years ago in Integrations 0 Future consideration

Need easier way to link to existing Jira records!

Current workflow from what we have determined and as was suggested by Aha support: 1. A new idea/suggestion comes in from a customer, we promote a new requirement in an existing Feature. 2. It is promoted to a new requirement. 3. Within about 30 s...
Jon DeLong over 2 years ago in Jira 0 Future consideration

Update of the UI of Settings -> Integration Updates

When navigating to the Settings -> Integration Updates, users sometimes find confusion on this being a notification to take an action item and accidently import various records. I propose the UI be changed so the users do not think they have to...
Russell Glenn over 3 years ago in Integrations 0 Future consideration

Integration Log "Type" Filter

As a workspace admin viewing the Integration Messages Log - I'd love to be able to click these buttons at the top of the log to filter just to "Errors" in red, "warnings" in yellow or "info" in blue - currently most updates are "info" and importan...
Karla Johnson over 2 years ago in Rally 0 Future consideration

Integrate Master Features and related features to different JIRA projects

In this scenario, there is one Program product workspace in Aha! and one Program project in JIRA which contains Master Features per Agile Release Train. All Stories (Aha Features) and sub-tasks (Aha Requirements) are with one or many Agile Teams (...
Guest about 5 years ago in Jira 1 Future consideration

When a feature is sent to Github that has images attached, can the images be shown inline rather than as links?

When I send a feature to Github that has images attached, the images show up in Github as links rather than inline which is how they would show up if I had created the feature in Github. It's easier and cleaner for our developers to see the images...
Guest almost 8 years ago in GitHub 0 Already exists