Mark

My feedback

  1. 6 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Mark supported this idea  · 
  2. 29 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Mark supported this idea  · 
  3. 156 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Mark commented  · 

    This is such a fundamental omission and has driven us to implement a third-party solution to separately query WIs and Test Management, performing the joins so that we can report on test coverage and requirement status.
    I can't emphasise enough how much this degrades VSTS as a viable ALM tool

    Mark supported this idea  · 
  4. 188 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Mark supported this idea  · 
  5. 323 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    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.

    Mark supported this idea  · 
  6. 310 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Mark supported this idea  · 
  7. 375 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    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 Hofman

    Mark supported this idea  · 

Feedback and Knowledge Base