While trialing this extension, we hit a confounding issue that will prevent our teams from using the extension. Our Product lead was adding notes to the work item while the team was talking through the estimate. A number of changes were made to work item fields as we worked to agree on an estimation value. A separate user - our Scrum Master - used the Estimate extension to save the estimated value. The Product lead then tried to save changes to the work item, and ADO gave the usual message indicating that changes to the work item had been made after the page was loaded. In this situation, the only option is to reload the page and lose all the changes.
Certainly this is a race condition in the core work item logic that could be mitigated by allowing the second user to choose what/how to merge - but that's something for the core Azure DevOps teams. In the meantime (maybe forever), it would be helpful for this extension to offer options that prevent the issue.
Options to consider:
Extension setting to disallow saving of estimation results to work items, with the setting scoped at various levels - org, project, team, area path
Save the estimation results in a way that doesn't create the race condition with other in-progress work item changes, such as adding results as a comment or as a link (or other creative option, each to be tested before running with any of these suggestions)
AminTi
commented
2 years ago
While trialing this extension, we hit a confounding issue that will prevent our teams from using the extension. Our Product lead was adding notes to the work item while the team was talking through the estimate. A number of changes were made to work item fields as we worked to agree on an estimation value. A separate user - our Scrum Master - used the Estimate extension to save the estimated value. The Product lead then tried to save changes to the work item, and ADO gave the usual message indicating that changes to the work item had been made after the page was loaded. In this situation, the only option is to reload the page and lose all the changes.
Certainly this is a race condition in the core work item logic that could be mitigated by allowing the second user to choose what/how to merge - but that's something for the core Azure DevOps teams. In the meantime (maybe forever), it would be helpful for this extension to offer options that prevent the issue.
Options to consider: