RELATED IDEAS
When using Import Records, not retaining parent/child relationship (AzDo Integration)
Who would benefit? |
Aha users when setting up a new workspace |
What impact would it make? |
Improves ability to only bring in needed records |
How should it work? |
After setting up integration mappings with parent/child relationships, have import records recognize those relationships. ie. If I import Epics, bring child records along with it (mirroring the parent child relationships set up in the mappings), instead of having to import epics, then features, etc. and having unparented records being processed. |
-
-
-
- +1
© 2024 Aha! Labs Inc.•All rights reserved
Here's my use case for this. Teams we're onboarding only want to import into Aha! their one initiative that's in progress, along with all of that initiative's descendant epics, features, and requirements items. The teams do not want to import their entire backlog because other older parts of the backlog are not up-to-date and may have data issues. The biggest data issue is that our Azure DevOps projects do not require items to be linked to a parent item. Teams cannot successfully import their many unparented items into Aha. We do not want the backlog data clean-up to prevent teams from using Aha! to plan and manage their one initiative that is in progress and has valid data.