Back in March, we shared an update on our initiative to make the New Boards Hub the default experience for all organizations. However, that rollout was delayed as we shifted priorities for several months. Today, we’re excited to announce that the rollout of the New Boards Hub is back on track. This process will take several weeks to complete, as we gradually deploy to a set of different regions each week.
Here’s a quick refresher on the New Boards Hub and what you can expect.
🤷♂️ How do I know New Boards is the default?
As we roll out to each customer, you’ll receive a welcome message the first time you open a new page in Azure Boards. If you come across this message, it means you’re now on the New Boards Hub.
🙋♀️ Is New Boards Hub better?
While the core functionality remains largely the same, you can expect the following improvements:
- Modern design
- Responsive reflows
- Enhanced performance
- Accessibility compliance
We’ve also introduced several new features that are exclusive to the New Boards Hub. For more details, check out the links below.
- Move to column position on Kanban board
- Assigned To children in Kanban cards
- Filter on work item history
- Move to column and move to swimlane
- Option to maintain hierarchy with filters
- Copy work item attachment URL
- Edit work item link types
- Copy link to comment
- Swimlane colors
- Sticky “Save” and “Save and Close”
- Swimlane rules
- Copy link to work item
- Markdown support on work item comments
- Team automation rules
- Add link to GitHub commit or pull request
- Show GitHub pull request details (preview)
- AB# links on GitHub pull requests (preview)
- Connect to GitHub repository search improvements
- Create GitHub branch from work item
🐞 What happens if I find an issue?
If you find a problem, please don’t turn off the New Boards Hub. Report the issue via Feedback Ticket or email me directly. We need to know if there is an issue so we can fix it. All feedback is appreciated.
The "Work details" feature had an "X" to close it, and now it requires two clicks (View Options + Off). This is strange because the planning option was integrated with the "X," creating two types of interaction.
I also noticed bugs in Work details, such as not calculating "Work by activity" correctly even when the "Capacity" setting is accurate.
This new version has a significantly higher padding compared to the previous one. The difference is so pronounced...
1) The issue with the X is a bug. It will be fixed in a couple of weeks for all organizations.
2) Work by activity works a little differently in New Boards. You have to assign the Task or Bug an activity. Before, it was looking at the person and what role they were assigned in the Capacity tab. We decided to simplify it a bit and just look at the Activity field.
3) yes,...
Just like to verify, if the “New Boards Hub” feature only applies to Azure DevOps Services and not on-prem Azure Dev Ops? We have Azure Dev Ops 2022 and we don’t see this feature enabled or configured.
Hello Neil. It is not available for on-prem yet. Our goal is to make it available in the next major version update. But the reality is, we need to make sure it is in great shape before pushing it to on-prem customer. Timing will be TBD depending on how things go over the next couple of months.
Is they a place for submitting Feature Requests for Azure DevOps?
When I get a message in a user story discussion adress to me I’d like to get notified in MS Teams preferably over Emails which I tend to look at only one a day while I am constantly in Teams chat with other workers.
https://developercommunity.visualstudio.com/AzureDevOps/suggest
Work item form with New Boards Hub preview enable: "Development" section let us add a link from a tfvc repository ("Link type: Versioned Item"). The "Item path" field includes the project by default, and we must inform the rest of the path to the source code we need to link.
Manually, this works Ok. But if we try to do this with the API call, the work item form shows 'versioned item link could not...
Sounds like a bug. Please email me the information directly and include the patch document you are using to save the link to the work item. If we can reproduce the issue, we will get it fixed.
The "Show more items" action when filtered for for @CurrentIteration still doesn't work.
This got marked as fixed here but still doesn't work; even the replies state that.
There are still a lot of reported issues regarding this feature and it drives us nuts. :-(
The latest fix for this issue is being released now. You should see it on your account in the next 3-5 days.