Skip to Main Content

Free trial
Join a demo

Share your product feedback

Ideas
Resources
Polls

Resources
Polls

Log in / Sign up

Please enter your email address

Home
A-I-8894
A-I-8258

Add a new idea Subscribe

2 VOTE

Status Future consideration

Categories Azure DevOps Services and Server

Created by Joe Granville

Created on Sep 21, 2019

RELATED IDEAS

New features created via an ADO integration are assigned to the parent epic release by default
Allow additional Link Types in the 'Links to' field
Features and Epics should move to integrated parent Release upon updates
Provide the ability to map the Release field from a Feature or Epic to an external system such as ADO
Ability to map an initiatives "assigned to" field with a user field within an integration
When a feature is linked to an existing epic in Jira, sync the child stories to Aha! as requirements
Aha Roadmaps- Provide ability to integrate with Themes
Show child initiatives nested under parent initiatives on the strategic roadmap
Add Release Reference field to the epic record for ADO mapping
Allow epics to be created for workspace line level

Allow parent mapping of releases to initiatives

In ADO we use assign our epics as children of themes. In AHA we map themes to initiatives and epics to releases but in the integration configuration we cannot set the parent mapping.

Attach files
Enter a subject
Drop here to upload

Idea management by

Aha!

Create your own ideas portal to crowdsource feedback

Products
Company
Resources
Popular links
Contact us

© 2025 Aha! Labs Inc.•All rights reserved

Privacy policy
Terms of service