Host Details:
OS Editon: Azure Devops server 2016
OS Build: 1607
Azure DevOps Details:
AZ server: 2019
The issue:
For one Team Project, we are requiring to have three different sub-area paths so we can place work there and Properly follow it.
The config:
Actually this configuration was able to been place in one oportunity, see bellow reference:
Because this approach introduce multiples advantages was decided to replicate it but, and here is when the issue starts not able to replicate with exact same parameters or via multiple attemp combinations, also tested under other landscapes with the same OS and AZ server,
which could be the issue? if before was possible as the screenshots proof it?
A Glimpse of other Attemp config:
Solved by myself
Hello Kevin, thanks for reaching me out so swiftly,
I did found the issue, due to a lack in Azure DevOps documentation didn't know that when creating a new Team Project have to create the extra teams within the Project before anything else, and then is that can proceed to add define the sub-area paths in the Boards Section and then is when is possible to have First multiple teams within a team project and Second have enabled the Work Items Button for each team sprint:
See for example this MS official documentation how they don't make any clarification of it: {{ https://learn.microsoft.com/en-us/azure/devops/organizations/settings/about-areas-iterations?view=azure-devops }} :
Also here {{ https://learn.microsoft.com/en-us/azure/devops/organizations/settings/set-area-paths?view=azure-devops&tabs=browser }} :
So MS docs miss that point completaly!