Sprint 219 was dedicated to fixing bugs. We continue to drive down the bug backlog as quickly as we can. We will also have a couple new preview features coming that will be announced in the 219 sprint notes.
Notable bugs fixed
|Delivery plans tab name||Browser tab name should reflect the name of the actual delivery plan.|
|Work item comment anchors||Anchor links for comments are not working.|
|Unable to remove picklist values||Unable to remove a value when customizing a picklist field.|
|System picklist values not showing||Missing custom values on system picklist fields when attempting to edit a field on the Kanban card.|
|Unable to create bug work item from task board||Unable to create a bug work item when creating it from an empty sprint task board.|
|Sprint backlog issues with switching tabs||Work items disappear when filter is applied and switching from sprint backlog to task board, and then to backlog again.|
|Error deleting attachment from preview||Receive an error when attempting to delete an attachment from the attachment preview screen.|
|Backlogs expand issue||Backlog hierarchy expands all nodes when adding a new child item to the backlog.|
|Cascading Picklist extension||Cascading picklist extension is not filtering out the list of values correctly.|
|Templates not loading values||Templets created in old boards hub are not populating field values when that template is being applied in the new boards preview.|
|Parents link not showing first||If you have a lot of work item links, the Parent link is not showing as the first link in the Related Work control on the work item form.|
|Column ordering on links page||Unable to sort on columns of the links page of the work item form.|
|Drag and drop re-ordering issues on large backlogs||Drag and drop re-ordering does not work correctly for large backlogs.|
|Assigning tasks on sprint board||When adding a new task to the task board, the iteration path is getting set to the Parent instead of the iteration you are currently on.|
|Permissions issues for links||If you have a link on the work item where you don’t have permissions, then all links are not accessible.|
|Sprint backlog and task board order||The order of work items on the sprint backlog does not always match on the task backlog.|
|Handling of commas in number fields||Numeric fields are not handling commas gracefully.|
|Using search and clicking work item link||Duplicate dialogs appear when using Search and clicking the link back to the same work item.|
|Shortcut issues on backlog||Insert shortcuts (INS or f+i) on backlog are not working.|
|Styles and empty date values||Styles on Kanban board that look at date fields are applying those styles for empty date values.|
|Markdown styling issues for Definition of Done||Definition of Done is not rendering correctly for some markdown elements.|
|Area and iteration level fields on CSV||Area and iteration level fields are not exporting to CSV.|
Note: although these items are fixed, they may not be released to all organizations yet. Rollout can take a few days to a couple weeks.
We appreciate and need your feedback to ensure the New Boards Hub is successful. Feel free to email me with any issues you find.
This so much. Even moving items on the Kanban/Task board now a days yield “Error” bars in the bottom of the cards forcing you to reload the page.
Is there any word on the issue that was reported quite a while back about the new UI failing to allow you to edit work items if there has been any changes made to the work item as part of the normal process? This was introduced with the new UI and has been broken for months even after being reported and sending examples. It is the one reason why I have recommended my team NOT use the new UI yet. For example you have a story open that you’re working on. In Visual Studio you submit a PR request associated with that story. You then jump to the story in the browser and attempt to change the state. It fails saying something has changed. Something has changed, a new PR link was added to the story. But this used to work just fine and doesn’t now. The only workaround is to not leave work items open or even the list of work items in a sprint. Refreshing the browser window solves the problem. But this is a little much to ask for from a common use case.
Another case, you have a story open with child work items. You click the child work item and that brings up the work item UI so you can change the state. You then close the child work item UI and are back in the story UI. You attempt to change the story’s state but it fails saying another change has been made. Again, you have to refresh the UI to get it to work again. This worked before the new UI and is having a detrimental impact on using the work item UI.