595 votes51 comments · Azure DevOps (formerly Visual Studio Team Services) » Administration & Licensing · Flag idea as inappropriate… · Admin →
I'm my company we have not used the One Project approach, and this is very annoying...
We need to build our own solution to be able to view all the projects status.
I really don't understand why Microsoft keep on developing tools like if only one project existed in a collection.
For example the new release feature is great, but again, its all per project! Task group, are... per project and not reusable from one project to another... why?
Please fix this, we are working on multiple projects!
323 votes30 comments · Azure DevOps (formerly Visual Studio Team Services) » Dashboards and Reporting · Flag idea as inappropriate… · Admin →
In our VSTS Feature Timeline(https://docs.microsoft.com/en-us/vsts/release-notes/), you see a feature called “Dashboards – Create dashboard separate from a team” under “Reporting”
This feature will allow you to create a Dashboard that has no association with the team. This means you don’t need to create a team, to make a Dashboard. You can create any number of these Dashboards and share them with who you want.
However, Dashboards will still be stored with a Team Project. So to address your scenario (cross-team-project Dashboard), you’ll just have to pick a team project to store the dashboard.
We don’t have immediate plans to store a dashboard outside a team project.
This would be good!
Not sure why in Microsoft word we work only on one project at a time.
I am in change of multiple projects so I need to keep track of all of them at once...
11 votes1 comment · Azure DevOps (formerly Visual Studio Team Services) » Release Management · Flag idea as inappropriate… · Admin →
This would be very useful indeed! not sure why this is not already available?
3 votesSlickRick shared this idea ·
Very VERY sad... :(