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.
375 votes5 comments · Azure DevOps (formerly Visual Studio Team Services) » Work Item Tracking · Flag idea as inappropriate… · Admin →
As explained in this blog post (http://blogs.msdn.com/b/visualstudioalm/archive/2015/10/08/how-we-use-user-voice-to-make-a-better-product.aspx), we had updated the status of this suggestion to “Under Review” to let you know we are tracking it on our backlog. To better indicate which one we are actively working on or which ones are on our 6-month plan, we introduced the states “Started” and “Planned”. The goal is to give an update on in progress suggestions at least every 3 months. This suggestion is still on our backlog, but they are not part of the 6-month plan.
Ewald HofmanSylvia Ward commented
What is the status of this request? I selected the link provided by the Visual Studio Team (see above post Oct 2015) but got an error. I do not see the status (e.g. Under Review" anywhere, and an update certainly has not been made every 3 months as mentioned.
This was requested many, many years ago and has been voted for over 350 times - what is the status?
We need this feature so we can hide some of our internal fields from the bug work item when it is opened up to our customer (who will be in a specific user group) to view the status. As mentioned by someone else, this functionality is available in JIRA, but we are a MS partner, so we have to use TFS/VS. We are using 2017.2 at the moment with plans to upgrade later this year.