Skip to Main Content
ADD A NEW IDEA

Integrations

Showing 944

The ability to review previously ignored integration candidates and undo the ignore

What is the challenge? Once you ignore an integration candidate, it is ignored forever unless you manually import or link the ignored record. If someone ignores a record by mistake there is no recourse to review those potential errors and correct ...
Stephanie Lechner 1 day ago in Jira 2 Future consideration

Sync Jira OOTB field values

What is the challenge? Out-of-the-box Jira field values cannot be synced, causing the inability to bidirectionally sync that field between Aha and Jira. What is the impact? Aha is meant to be the singular solution for Product teams to set their st...
Michael Tucker about 22 hours ago in Jira 0

Ability to update Jira Affects Versions field from Aha via integration

What is the challenge? Our Jira project has the Affects Versions Jira field configured as a required field. The integration only allows for a uni-directional update from Jira to Aha so I get an error when pushing Aha items to Jira. Because of this...
Kevin Scribner 3 days ago in Jira 0

Map detailed estimates by initiative in Jira integration

What is the challenge? Right now, you cannot map detailed estimates by initiative. You can only map estimates for Epics, Features, and Requirements. What is the impact? When trying to estimate at a higher level and leveraging initiatives, you cann...
Kelly Fogus 3 days ago in Jira 0 Future consideration

Send ideas to Jira

What is the challenge? Companies that use both Jira and Aha! ideas must go through extra steps to send information between the two systems. For example, if a small fix comes in as an Aha! idea, it must first be promoted to a feature or requirement...
Kelly Sebes 6 months ago in Ideas / Jira 4 Planning to implement

Allow automatic imports of child records when parent records exist in a different workspace

What is the challenge? Currently, for Jira integrations, when you have parent/child records in Jira that span multiple Jira projects connected to multiple Aha! workspaces, all child records created will need to be manually approved as an integrati...
Stephanie Lechner 7 days ago in Jira 0 Future consideration

Move epic/feature to default release when integrations unlink the release

What is the challenge? When an integrated epic or feature is moved in a dev tool (Jira or Rally) to an "unscheduled" release, the relationship in Aha! is null and no change occurs. This is problematic because the release was changed but the Aha! r...
Jeanette Resnikoff 17 days ago in Integrations 1 Planning to implement

Rally Project name change should be reflecting in the Aha! Integration

What is the challenge? Rally Project name is updated but the project name is not updating in the Aha Integration Project Tab? What is the impact? Users see the wrong project name in the Aha integration and think they need to create a new integrati...
Mike Jacobson 5 months ago in Rally 1 Already exists

Features and Epics should move to integrated parent Release upon updates

What is the challenge? If you introduce Version<>Release mapping to an existing integration or you link a record to an existing Jira record, subsequent updates are creating a new Aha! release (linked to the Jira issues's Fixed Version) but t...
Stephanie Lechner about 1 month ago in Jira 0 Planning to implement

Azure DevOps Integration - Sync dependencies at UserStories/Requirements level

What is the challenge? Currently, Aha integration with ADO syncs dependencies at Features level only. We need to also be able to sync the dependencies at Requirements/UserStories level.Including dependencies between Features and User Stories. What...
Guest 5 months ago in Azure DevOps Services and Server 0 Future consideration