Get started for free
Note: Forums will be making significant UX changes to address key usability improvements surrounding search, discoverability and navigation. To learn more about these changes please visit the announcement which can be found HERE.
Visual Studio Developer Center >
> 
> 
How do you indicate a bug is blocking QA from moving forward?

Answered How do you indicate a bug is blocking QA from moving forward?

  • Monday, July 23, 2012 4:49 PM
     
     
    Sign In to Vote
    0

    If the "blocked" field is supposed to be used to indicate an issue is blocking progress toward resolution of a particular bug, how do you indicate that a particular bug is blocking QA from moving forward with testing in a given area?  Would you submit an Issue work item?  Seems like double work for both QA and Dev.

    Jolene Boumeester

     

All Replies

  • Monday, July 23, 2012 11:15 PM
     
     
    Sign In to Vote
    0

    Hello Jolene,

    What template are you using?  Scrum, Agile or CMMI?

    Each of these has different layouts for the Bug work item.

    If you need a blocked field, you can modify the template to add a blocked field similar to the one in the story.

    You need to supply a few more details.

    - Bruce

    Bruce

     
  • Wednesday, July 25, 2012 12:18 PM
     
     Answered
    Sign In to Vote
    0

    Blocked or lets call it impediment is used to indicate that the bug or work item is being held back because of x issue. 

    Again as bruce mentioned you need to supply more details about the process template but in general you flip the status of your work item to blocked and create a sub work item to indicate the reason for blocking. 

    To create an impediment and link it to a product backlog item

    1. On the Links tab, click Add New Linked Work Item New.

      The Add new Linked Work Item dialog box opens.

    2. In the Link Type list, click Related.

    3. In the Work Item Type list, click Impediment.

    4. In Title, type a name that describes the blocking issue as specifically as possible.

    5. (Optional) In Comment, type additional information.

    6. Click OK.

      A work item form for an impediment opens and shows the information that you have provided.

    7. Define the remaining fields, and then click Save Save Work Item.

      For more information about the fields on the form for an impediment work item, see Impediment (Scrum).

    Please remember to mark the replies as answers if they help.

    Tarun Arora

    Blog: http://geekswithblogs.net/TarunArora  Subscribe in a reader

    Facebook: Visual Studio Bytes

    Videos: ALM Videos

     
  • Tuesday, July 31, 2012 10:29 PM
     
     
    Sign In to Vote
    0
    We're using the CMMI template straight out of the box.  Our problem is that while we understand what the Blocked field is supposed to be used for, we're not sure how to indicate that QA cannot move forward until a particular bug is fixed.   Is the correct process to submit an Issue work item?  It would be nice to be able to flag a particular bug as "hot" so the developers know to work on it first.  I do understand priority can also be used, but if the Blocked field (or some other field) could be used for this purpose it would make querying much easier.

    Jolene Boumeester