ADD A NEW IDEA

FILTER BY CATEGORY

Integrations

Showing 199 of 6629

Add missing Rally built in fields "Project" and "Leaf Story Plan Estimate Total" in Aha! under Integration field mapping

The following fields are available in Rally but are not available in Aha to do field mapping under Aha to Rally Integration. Please add these fields so that teams can map them.Rally Built in field names:ProjectLeaf Story Plan Estimate Total
Uma Prabhala 6 months ago in Rally 4 Shipped
172 VOTE

Please add support for Master Features within the Aha <=> JIRA interface.

Given "Aha! is for the "why" and "what" and JIRA is for the "how."; Master Features are useless unless we can implement them alongside JIRA.
Guest over 3 years ago in Jira 28 Shipped
163 VOTE

Support aggregating Features into Sprints - and pushing into JIRA as a SPRINT

We need to be able to manage our Features, grouping them into SPRINTS and then pushing the sprint and features into JIRA as a complete set, ie. creating the SPRINT and associated JIRA Tickets. Because the support for SPRINTS doesn't exist in Aha, ...
Cynthia Countouris about 4 years ago in Jira 17 Shipped
111 VOTE

Integration with Microsoft Teams

Our organization is moving from Slack and into using Microsoft Teams. We would like to have our Aha! activity feed integration be compatible with Teams.
Jon Kremer almost 4 years ago in Integrations 20 Shipped
134 VOTE

Aha! + JIRA feature/story relationships (e.g. is blocked by, depends on) should match

If one feature depends on another, and you create that dependency in Aha!, it will not be reflected in JIRA currently. If Aha! and JIRA feature/story relationships were maintained back and forth, then we could create more realistic roadmaps and st...
Guest almost 5 years ago in Jira 22 Shipped
141 VOTE

As a developer, when I change a story's epic / fix version (i.e. Aha! feature / release) I want that change reflected in Aha! so that my Product Manager will know that a story or bug was pushed out to the next release

No description provided
Yen Pham over 5 years ago in Jira 25 Shipped
111 VOTE

Ability to link features/requirements to existing VSO work items

Current VSO/TFS integration only allow to submit a feature/requirement from Aha! to TFS/VSOAn option to link a feature/requirement with an existing TFS/VSO work item would be helpful
Joris van Doorn almost 5 years ago in Azure DevOps Services and Server 23 Shipped

Support the "links to" field mapping with next-gen templates in Jira

My team really likes the simplicity of the "Agility" templates in Jira, sometimes called "next-gen" templates. Through the Jira integrations, we are able to sync almost everything that we need, except for the relationships using the "Linked to" ...
Jordan Skole about 2 years ago in Jira 12 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 almost 3 years ago in Integrations 7 Shipped

Jira Integrations 2.0 support for time tracking

Support synching the work logged from JIRA to Aha! in 2.0
Karen Maslowski almost 3 years ago in Integrations 11 Shipped