RELATED IDEAS
Update the Feature % Complete field based on User Stories of the DevOps Feature
Update the Feature % Complete field based on User Stories of the DevOps Feature that is linked to the Aha Feature.
The Software Product Plan does just that!
In DevOps, this information is a calculated field, which can be easily configured in Boards.
After our PM team agrees with the R&D team the features that will be executed and then we link the Aha features with the DevOps Features, what we expected was that the Feature % complete could be updated automatically. What doesn't happen. It only works if you link all the Requirements with the User Stories one by one.
However, what happens is that if, it will be necessary to keep monitoring all the time if a DevOps feature had new User Stories created or deleted (which will affect the % completed calculation) and then manually create or delete the requirements in Ahah. In this way, there is no benefit in the integration.
1
MERGED
Update the Feature % Complete field based on User Stories of the DevOps Feature
Update the Feature % Complete field based on User Stories of the DevOps Feature that is linked to the Aha Feature. The Software Product Plan does just that! In DevOps, this information is a calculated field, which can be easily configured in Board...
0
Future consideration
After investigating, we found that the
Progress by story pointfield from the DevOps board isn't accessible via the API. We hope Microsoft will support this in the future. In the meantime, we changed this idea's status back to "Future consideration".Hi there, thank you for the idea! The progress field is a mappable field in integrations, but when we built it there was not a corresponding progress field available in DevOps (so some teams would connect it to a custom field.) From your screenshot though, it appears there is now a field that is automatically calculated. Can you confirm the name of the field on the DevOps side? Thanks!