-
Notifications
You must be signed in to change notification settings - Fork 15
Label index
Issue
Identifies any software defect that affects the running or quality of the product. Anyone with access to the GitHub repository can create Bugs, but only the Test team should close the bugs. We can't enforce this via software but issues not closed by the Test team will be re-opened.
Category
Tags categories that are used for organizational purposes
Completed
Marks a task that has been checked into a branch but not into a build
Document (internal use only)
Internal label to identify issues that require documentation for the next release
Duplicate
Marks a bug that is matched with an already known issue.
Epic
Identifies a large user story that would take a significant time to complete. (e.g. 3-4 weeks)
External Dependency
Marks an issue that is not in the Visual Studio plug-in but found in dependent software
In Progress
Marks a task has been assigned to a member of the Development team and is in the process of being completed
Known Issue (internal use only)
Marks an issue that should be included into the official release notes/known issues list
Not a Bug
Indicates that the issue raised is not considered a bug by the VS team
Not Reproducible
Marks an issue that has been tested and is not able to be reproduced
P1
Marks an issue that would severely impact the use of Visual Studio (e.g. crashing, loss of user data)
P2
Marks an issue that is highly visible or impacting, but for which there are known workarounds
P3
Marks an issue that is not considered P1 or P2
Product review
Marks tasks that Product Management will review and assign priority. Also marks items that Contributors suggest that we should add to our backlog that will be reviewed by Product Management. Also indicates a user story that needs to be closed.
Recommended Closure
Marks a bug that cannot be reproduced. It can also be used to label an old task, or a task where there is no intent to fix.
Suggestion
Marks an issue that Contributors suggest that we should add to our backlog
Task
Used by the Development team and the Test team to break down User Stories into manageable units of work for tracking purposes. Tasks should either be closed by the task owner when they have completed the task, or re-assigned when the task needs to be handled by someone else.
Tech (internal use only)
Used for tasks that require no testing from the Test team or tasks that can only be tested by the Development team
Testing Task (internal use only)
Identifies tasks that are created by the Development team to indicate what should be tested for this feature or tasks for the Test team in general
User Story
Identifies any functionality that Product Management wants added to enhance the feature set of the application
Verification Passed (internal use only)
Identifies an issue that the Test team has tested and has passed the criteria
Verification Failed
Identifies an issue that the Test team has tested item and has failed the criteria; the item needs to be returned to development