Christopher Schleiden

@bdmurray Thanks for making this change! Created a PR from your branch and merged it. I'll double check later and then release a new version with the change.

That's fair. What do you think about showing the actual field name - since it could be different for each work item type?

I played with this a while ago but haven't gotten to it yet: 

No, they are deleted. The actual values are stored in the work items. Is there anything you'd need from deleted sessions?

This is still planned, however, the problem is not adding new work items to a session, that's fairly easy to build. The difficulty is somehow selecting the work items. The...

I guess adding a refresh button in the overflow to re-run the query/fetch the iteration for all users would be a nice addition, too. Filed #32

Please try upgrading to 2019 Update 1: https://docs.microsoft.com/en-us/azure/devops/server/release-notes/azuredevops2019u1?view=azure-devops

Good point, we could update to something like: ``` { "targets": [ { "id": "Microsoft.VisualStudio.Services.Cloud" }, { "id": "Microsoft.TeamFoundation.Server", "version": "[15.0,)" } ] } ```

You can click on the Id + Work Item Type to open in a dialog/new tab: 

This is difficult since work item types could have any shape or number of fields. For now the logic is to look at the `Details` page of a work item...