Bug
A Bug is a record that identifies a potential source of dissatisfaction with the product or release. Teams have been capturing and reporting bugs for many years. The work to close bugs takes time and needs to be captured within the overall project schedule. This form is very similar to traditional Product Studio bug, with a few twists to keep things fresh. We know teams will customize this work item type, but the goal is to keep it simple.

Required Fields
Title
: Unique title for the Bug

Assigned to: Individual responsible for the fixing the Bug

State: The state of the Task. The workflow for the states is as follows:
    Active: This is the default starting state. Bug has been approved and work is being completed to execute against this release
    Resolved: Bug has been resolved and waiting for confirmation
    Closed: Bug is completed, cut or should be ignored




Priority: Priority for the Bug. Choices are:
    1: Must Fix
    2: Should Fix
    3: Nice to Fix
    4: Wish List
 

Optional Fields
Severity
: Severity for the Bug. Choices are:
    1: Bug causes crash or data loss
    2: Bug causes major functionality problems
    3: Bug causes minor functionality problems
    4: Bug contains typos, unclear error messages or wording

Rank: Numeric field individuals can use to sort their bugs

Found In: Build stat

How Found (Category): Choices are:
    Accessibility
    AdHoc
    Build Break
    BVT
    Dog Fooding
    External
    Globalization
    Localization
    Performance
    Usability

KB Article Ref: Build Stat

Keywords: Freeform field that teams can use for tagging bugs

State Driven Fields
The following fields are populated or available as the bug moves through the different states:
Status:
    Changed Date: the date the bug was changed
    Changed By: the individual that changed the bug
Opened:
    Activated Date: the date the bug was activated
    Activated By: the person that activated the bug
Resolved:
    Date: The date the bug was resolved
    By: The person that resolved the bug
    Integration Build: The build the bug was fixed in
    Reason: How the bug was fixed. Choices are:
        By Design
        Duplicate
        External
        Fixed
        Not Repro
        Postponed
        Won’t Fix
    Duplicate ID: The ID of the duplicate bug
Closed:
    Date
: The date the bug was closed
    By: The person that closed the bug

Tabs
Description
: Free form text for the description of the Bug

History: Standard tab to track all changes to the work item.

Links: Linking information

Dependency: Dependency parent details for this bug:

Dependent System: The system the dependent bug is stored within(Team Foundation Server or Product Studio)

Project (Server): Name of the Server and/or Project

ID: Unique ID of the dependent bug

State: State of the dependent bug

Resolution: Resolution of the dependent bug. Choices are:
    By Design
    Duplicate
    External
    Fixed
    Not Repro
    Postponed
    Won’t Fix

Changed Date: Change Date of the dependent bug

File Attachments: Supporting documentation