Share your product feedback

Add a new idea Subscribe
Status Likely to implement
Categories Integrations
Created by Guest
Created on Feb 27, 2024

RELATED IDEAS

Iteration to Release not Retaining Parent Relationship with other Records (AzDo Integration)

Who would benefit?

Aha users

What impact would it make?

Elimination of lost records (Azdo integration)

How should it work?


When using iteration to release, the integration would look at the area path of that record as well as the iteration path.

Scenario:

  1. Iteration path changed for work item A to 2024 but that release is not linked in the workspace that work item A is currently in.

  2. Multiple workspaces use 2024 iteration

  3. Instead of that work item being automatically moved to another workspace and it's integration link removed, check the iteration path and area path. If the release doesn't exist in the workspace for that work item, move to parking lot. Retain parent child relationship with initiatives, epics, features
  • Attach files
  • Aha!
    Nathaniel Collum
    May 16, 2025

    I have an idea for how integrations could support this.

    Use current workspace as anchor

    • When syncing an iteration change from ADO, check if the current Aha! workspace has a release linked to that iteration. If so, update the record to that release. Only fall back to other workspaces if no match exists in the current one.

    • This approach assumes:

      • The user has placed the record in the correct workspace.

      • That workspace has a release linked to the ADO iteration.

    • If both are true, Aha! should treat that release as the correct destination — instead of scanning all workspaces for a match.

    3 replies
Idea management by Aha!
Create your own ideas portal to crowdsource feedback
© 2024 Aha! Labs Inc.•All rights reserved