Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 631

Integrate to-dos with Rally tasks

It would be great if the "to-do's" in AHA Requirements, can be mapped to Rally as "to-do's" in the users stories. And, update both ways if marked as completed. Here is a similar idea for Azure DevOps; it would be great to see this for Rally as wel...
Guest about 3 years ago in Rally 0 Future consideration

Allow 2-way integration to Jira FixVersion/s field from text field

Instead of having to integrate Aha! Release to Jira FixVersion/s, let Aha! text fields specify the name of a version and have it update the FixVersion in Jira based on a matched name. If no matched name exists, then throw an integration error just...
Jor Bratko about 3 years ago in Jira 0 Future consideration

Importing data from Rally to Aha using “Import Records – Grid query” functionality

When we import data from Rally into Aha using “Import records – Grid query” functionality it does not give option to select a release in that workspace but rather imports all the data into a Parking lot. Users have to manually move all that import...
Karla Johnson about 3 years ago in Rally 0 Future consideration

Allow two-way integration for picklist fields in Azure DevOps when using the XML process model

This idea is a variation on https://big.ideas.aha.io/ideas/AFME-I-2, but the general use case is the same. I've been asked by Aha support to make a separate idea specifically for those using the XML process model, since this has supposedly been fi...
Tessa Adair about 3 years ago in Azure DevOps Services and Server 0 Future consideration

use Jira credentials of the user to record changes in Jira

In the Aha! user profile, request the Jira credentials of the user. When making updates to Jira tickets, use these credentials so that we can see in the JIra ticket who actually mae the update. Kendis does this.
Guest about 3 years ago in Jira 0 Future consideration

Pivotal Stories added to Epics converted to Requirements in Features

The Pivotal integration is good, but fails to capture a common case for us. Our teams often add new Stories to Epics that are essentially Requirements on the corresponding Feature. We track progress through these Stories/Requirements. Right now, t...
Christopher M about 3 years ago in Pivotal Tracker 0 Future consideration

Send events before deletion

We currently sync a field in Aha! to Jira when a record is created. We’d like to clear that field if the record is deleted from Aha! I’m looking to send an update to the field or set an event trigger to make a note that the field value has changed.
Yancey Larochelle-Williams about 3 years ago in Jira 0 Future consideration

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 about 3 years ago in Jira 0 Future consideration

Update Asana integration to use milestones

Asana introduced Milestones in 2020. These are closely analogous to Aha releases. The only option to link a release in Aha is to a column in Asana - I guess because there was no Milestone at the time. This is now not ideal and means that we cannot...
Guest about 3 years ago in Asana 0 Future consideration

Configure iterations based on phases in DevOps

We're using multiple layers of iterations within Azure DevOps. So a Release consists of multiple sprints. I would like to be able to map not only releases to iterations, but also phases to iterations. That way I can use Aha! as a single point of e...
Carlo Bril about 3 years ago in Azure DevOps Services and Server 0 Future consideration