Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 253
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 about 7 years ago in Jira 28 Shipped

Allow setting "Parent" field for "classic" Jira project issue types other than sub-task

The new Epic/Parent link field for Jira is only supporting for NextGen projects. Classic projects need to be supported as well.
Bonnie Trei 4 months ago in Jira 0 Shipped

Enhance aha to github integration to include Projects Beta

We started looking into testing the integration with github.com and aha and noticed that Github has new functionality ‘Projects Beta’ which gives users spreadsheet like functionality to group issues and pull requests (screenshots attached). These ...
Guest about 2 years ago in GitHub 11 Shipped
166 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 over 7 years ago in Jira 17 Shipped

Update Jira integration to use "Parent" instead of "Parent Link"

Who would benefit? Anyone using Jira integrations What impact would it make? "Parent Link" and "Epic Link" fields have been replaced by a new "Parent" field in Jira. By recognizing this new field, integrations will not break and can use the new fu...
Meg E 5 months ago in Jira 2 Shipped
136 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 over 8 years ago in Jira 22 Shipped
142 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
Guest almost 9 years ago in Jira 25 Shipped
135 VOTE

ServiceNow integration

Ability to create and manage ServiceNow epics through Aha! Product Management would define the epics and they would flow down into ServiceNow
Guest over 8 years ago in Integrations 31 Shipped
112 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 over 7 years ago in Integrations 20 Shipped

Guide users to reload configuration when missing field in mappings

When new fields are added in the development system, they are not automatically shown in the Aha! integration mappings screen. Users do not intuitively know to click the "Reload configuration" button, and also do not know to check the Jira create/...
Madeleine Black over 1 year ago in Jira 0 Shipped