Skip to Main Content
Status Future consideration
Created by Dan Orth
Created on Aug 31, 2021

Better handling of when Features are removed from a Sprint

In our Aha / Azure DevOps integration we are mapping sprints back to Aha using a custom field, similar to this article:

The issue seems to be that if a Feature is removed from a sprint (i.e. no iteration level 3 field in ADO), the custom field in Aha is not updated to reflect that. I would expect the custom sprint field to be blank. Instead Aha is showing the last sprint/iteration level 3 that the feature was assigned to.

Since I lock the custom sprint field in Aha (it's one way from Azure DevOps -> Aha) it is problematic to correct this manually.

  • Attach files