ADD A NEW IDEA

Integrations

Showing 948

Support bi-directional flow of data when mapping Aha! releases to Jira sprints as a field mapping for features

Use case: Aha! releases are mapped to Jira sprints as a field mapping under features. Currently this mapping is only supported in one direction, Aha! to Jira. It would be helpful if this mapping supported the flow of data in both directions.
Dale Potter almost 4 years ago in Jira 0 Future consideration

Need to be able to connect Google Drive files

Looks like Aha! is not approved by Google's application security process? This is a huge issue for us as we are in the middle of planning for upcoming quarters and using Aha! for the first time. Is this likely to be fixed in the future? Is there a...
Shosh almost 2 years ago in Integrations 2 Will not implement

Support acceptance criteria for a requirement, enable sync of acceptance criteria with TFS

each requirement should have an acceptance requirement section that can sync to a user story acceptance criteria in TFS
Guest almost 6 years ago in Azure DevOps Services and Server 1 Already exists

Filter capabilities on the Integration Update Import screen

As one Product Owner of a very large product that has a lot of product owners, I would like more filter capabilities on the Integration Updates import screen so that I can only see items that pertain to my portion of the backlog. This request is s...
Guest almost 2 years ago in Azure DevOps Services and Server 0 Future consideration

Parent version mapped to 2 different releases - let user decide where to import

The same Jira version may be associated with releases from more than one Aha! workspace. This can happen when different products in Aha! are all being released together. When auto-import is enabled on the integrations and a new record is created i...
Mark Crowe about 4 years ago in Jira 0 Future consideration

Allow existing Trello comments to be imported

The integration version of Trello import/export doesn't allow importing comments from Trello cards that existed prior to the integration/sync. This prevents us from retaining significant discussion about a feature (or idea) in the Aha copy of the ...
Guest about 6 years ago in Trello 1 Future consideration

Allow Integration variable on Create Record layout

Currently when creating a feature, I have to create the feature and then manually send the integration to ADO. I want to have a variable on the Create Record Layout screen to be able to choose this option when creating the feature. This way I can ...
Kalyndra Craven about 4 years ago in Azure DevOps Services and Server 0 Future consideration

Ability to pass relation link between features into VSTS

When an item is too big for a single feature and has to be broken up it would be great to be able to have the relationship link in AHA pass the same relationship when integrated with VSTS so that the developers know that the User Story they are wo...
Guest about 6 years ago in Integrations 0 Future consideration

Interface AHA! "To Do's" into MS TEAMS/PLANNER

This would allow the project management team to review and manage the project in AHA! and collaborate with Global teams on MS TEAMS by integrating the tasks.
Shane SWINEHART about 4 years ago in Integrations / To-dos 0 Future consideration

Add the ability to combine fields with GitHub Integration

We need the ability to send more information from Aha to GitHub, this would include the Due Date.   We need the ability to combine fields from Aha to a single GitHub Field.   E.g.   Send Title + Due Date in Aha to the Title Field in...
George Champlin-Scharff about 6 years ago in GitHub 0 Future consideration