We’ve reached a major milestone in the rollout of New Boards Hub this week by making it the default experience for all organizations and users. While many users can still temporarily switch back if they encounter a blocking issue, our telemetry shows that 97% of users are staying on New Boards without reverting. This is a significant step forward!
Maintaining two versions of Boards is not a sustainable long-term solution, and our goal is to transition all customers to New Boards permanently. To that end, we’ve already disabled Old Boards for over 50% of organizations, and we’ll continue this process over the next two to three months.
🗓️ Migration Timeline & Expectations
The timing of your organization’s permanent transition to New Boards depends on its location. Many organizations have already been migrated. If your organization still has the option to revert to Old Boards, you can expect the transition to happen during one of the following time periods:
- March 10 – 21
- April 14 – May 5
By early May, all organizations will be fully moved to New Boards, and Old Boards will no longer be available.
📣 Your Feedback Matters
It’s not too late to share your feedback! I’ve been actively reviewing and responding to all submissions. However, please note that some design decisions, such as padding and spacing, will not change in the short term. These were carefully considered to align with the other Azure DevOps hubs.
That said, we are making targeted improvements based on user input. For example, we’re refining query results to maximize data visibility and reduce wasted space. It’s always a balancing act, but we’re committed to making meaningful adjustments where they add value.
If you have feedback, please submit an issue through the Developer Community site.
🙏 Thank you
Thank you for your time and patience throughout this process. It’s been a long three-year journey, and we’re excited to bring it to a close so we can focus on bringing new value to Azure Boards.
We appreciate your support and look forward to what’s next!
Dan,
I did use the backlog settting rule for "Activates the parent work item when at least one child has been activated." and "Complete the parent work item when all children are completed."
So a created an Epic, then one Feature and finnaly an User Story (each a child of the previous one).
Then I closed User Story, the most elementary of child and open "Epic level" board.
I've got that error (which forced me to refresh the page):
An unexpected error has occurred within this region of the page.Read more
You can try reloading this component or refreshing the entire page.
Sorry Carlos. I don’t really understand the issue. Please post the issue to https://developercommunity.visualstudio.com and make sure you do a full screen recording so we can see what you see.
Hi Dan,
Something went wrong with this new version.
In the past I was able to see all my work items on the board, but now that is no longer the case.
Some work items I can retrieve from the query, but I can't see them on the board.
For our company this is a big problem because sometimes I need to use the board filter to get a specific work item based on the fields in its cover -- because I don't know its ID.
If I lose this ability, I will no longer be able to work with...
You should certainly be able to see all and filter the items on the Board. But keep in mind, we do limit the number of items that we return in the New and Closed columns on the initial load. And filters are driven by the data that is loaded. For example, if you have a work item at the bottom of your backlog, it is not likely going to be loaded on the initial load. To solve this, you can use the "load more items" in the New column. Each time you click that; we load another set of work...
Hello, the welcome message above seems to be an image, and I can’t click the link or next button. Can you provide the link or is it the just the text above.
It’s just an image to show you that New Boards is rolling out 😁. You should have seen the popup at least once in the last few weeks since everyone has been moved to New Boards by default.
With the new hub dashboard, we are facing the issue of bulk importing (creating/editing) items of work item type Test Case in ADO.
this used to work with the feature disabled
Getting this error
Found field value error(s):
Forbidden work item type “Test Case” specified in column Work Item Type at line 2, column(s) 1.
This is by design. We removed that feature from the general work item import because test cases, with steps and params, are much more complicated. You should use this instead: https://learn.microsoft.com/en-us/azure/devops/test/bulk-import-export-test-cases?view=azure-devops
Hi Dan,
I would like to know the timeline for the Azure DevOps Server (on-prem)?
We don’t have a timeline set yet. We want the New Boards to bake for a while in the service to make sure it is ready for on-prem. We should have something to share by June or July.
I’ve switched back because I found bugs immediately – just like every time I’ve tried the new UI before.
I’ve reported the bugs on your Developer Community site. They were immediately closed as “Lower priority”.
So you won’t be fixing bugs, but you’ll also take away the old (working) UI. This is a really bad experience!
Manual, thanks for the links. I will review and respond to them inline.
Please share the links to the bugs we’ve closed, and I’ll review them. As mentioned earlier, we prioritize issues based on the feedback received. While we’d love to address every concern, some issues will be lower priority, especially if they have minimal impact. If only one person reports a problem, it’s unlikely to be a priority at this time. However, if multiple people report the same issue, we will likely address it.
These are the bug reports:
https://developercommunity.visualstudio.com/t/New-Boards-Hub-textbox-scrolls-to-top-af/10864382
https://developercommunity.visualstudio.com/t/New-Board-Hub-doesnt-return-to-linked-i/10864394
I understand that you can't fix every small issue - at least not immediately. And I wouldn't care if I could continue to use the old UI. But please understand that I'm frustrated if I'm forced to use a new UI that has a worse UX.
Also, about the point "If only one person reports a problem": Something similar was also written in the close note of the bug reports ("based on the votes and comments from others in the community"). But how can other users report the same problem (or vote/comment) if the report...