![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 80%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAI%3C/text%3E%3C/svg%3E)
4,144 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 32%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
Actually that is how Azure DevOps works AFAIK. Work item IDs are unique within an organization irrelevant of projects. DevOps supports querying across projects in queries.
Within the web portal you can limit visibility based upon user groups set up at the project level. However as documented in the APIs this is not enforced at the API level. Therefore if you have read permissions to an organization you can query for work items irrelevant of what project created them. Same thing with write privileges. Hence the project part of the URL is for resources that need it and consistency but does not necessarily have any impact on what is and isn't visible at the project level. It would depend on the individual resources whether the project has an impact. For example querying for a project's dashboard would care about the project but accessing work items (that are shared across all projects) doesn't particularly care provided it is a valid project in the organization.