Critical Bug - Active work item document does not exist in the current context about azure-devops-extension-sdk HOT 5 OPEN

I have the same issue. If you disable the New Boards Hub feature then it works for me.

from azure-devops-extension-sdk.

We also experience the same problem. Is there a chance to get things going with that?

from azure-devops-extension-sdk.

Recently, I followed a link that leads to this bug, and it was closed, and Azure DevOps started working as expected. Why has the bug reappeared?

from azure-devops-extension-sdk.

With the old Boards Hub the azure-extension-sdk will report the current work item as the one in background window (work item 13 above). When creating a new work item, a modal will appear and and the sdk will provide that work item's id (work item 7 above) as the current work item - not so for with New Boards Hub enabled - then it will always provide the background work item as the current work item.

Now, with the New Boards Hub clicking any work item links will open this in a modal - that is new behaviour. In fact, you can have many modals open on top of each other. With the old Boards Hub you only get the modal when creating a new work item.

What we need, is access to the stack of modals so we can get the appropriate IDs.

from azure-devops-extension-sdk.

With the old Boards Hub the azure-extension-sdk will report the current work item as the one in background window (work item 13 above). When creating a new work item, a modal will appear and and the sdk will provide that work item's id (work item 7 above) as the current work item - not so for with New Boards Hub enabled - then it will always provide the background work item as the current work item.

Now, with the New Boards Hub clicking any work item links will open this in a modal - that is new behaviour. In fact, you can have many modals open on top of each other. With the old Boards Hub you only get the modal when creating a new work item.

What we need, is access to the stack of modals so we can get the appropriate IDs.

Martin, have you tried to resolve this issue? Maybe by getting the ID through some library method? Possibly using the onLoaded or onRefreshed methods?

https://learn.microsoft.com/en-us/azure/devops/extend/develop/add-workitem-extension?view=azure-devops#addmenuaction

By the way, I tried turning off the New Boards Hub, and the bug really went away. After I turned the New Boards Hub back on, the bug did not reappear.

from azure-devops-extension-sdk.