Label index

The labels in the BlackBerry Native Plug-in for Microsoft Visual Studio project are used to identify the status of an issue within the project. More than one label can be applied to an issue.

Blocked
Marks an issue that can’t be verified because it is blocked by another issue

Category (Internal Use Only)
Marks categories that are used internally to organize issues

Completed
Marks a task that has been checked into a branch but not into a build

Document (Internal Use Only)
Marks an issue that requires documentation for the next release

Duplicate
Marks an issue that is matched with an already known issue

Epic
Marks a large user story that takes significant time to complete (for example, 3-4 weeks). An epic is any functionality that Product Management wants added to enhance the feature set of the app. Only Product Management should add an epic to the backlog or close an epic.

External Dependency
Marks an issue that is not in the 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

Issue
Marks any software defect that affects the quality of the product. Anyone with access to the GitHub repository can submit an issue, but only the Test team should close issues. Any issues not closed by the Test team will be re-opened. The Issue Originator has 10 business days to close the issue after it has been fixed. If the timeframe is exceeded, the Test team closes the issue.

Known Issue (Internal Use Only)
Marks an issue that should be included in the official release notes/known issues list

Not an Issue
Marks that an issue is not considered an issue by the Development team

Not Reproducible
Marks an issue that has been tested and is not reproducible

P1
Marks an issue that severely impacts the use of Microsoft Visual Studio (for example, crashing or 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 a P1 or P2

Product review

• Marks tasks that Product Management reviews and assigns priority
• Marks an issue that a Contributor suggests should be added to the backlog
• Indicates a user story that needs to be closed

Recommended Closure

• Marks an issue that cannot be reproduced
• Marks an issue as old or there is no intent to fix

Suggestion
Marks an issue that is submitted by a contributor for a new feature request. The suggestion is reviewed by Product Management and, if accepted, is added to the backlog. If it is not accepted, it is closed and a response is sent to the contributor. Suggestions are reviewed within five business days of submission.

Task (Internal Use Only)
Marks a unit of work that is used by the Development team and the Test team to break down user stories for tracking purposes. A task is either closed by the task owner when the task is completed, or re-assigned when the task needs to be handled by someone else.

Tech (Internal Use Only)
Marks tasks that do not require testing from the Test team or can be tested only by the Development team

Testing Task (Internal Use Only)
Marks tasks that are created by the Development team to indicate what should be tested for a feature or tasks for the Test team in general

User Story
Marks any functionality that Product Management wants added to enhance the feature set of the app. A user story must have well defined end user benefits with clear testing criteria. Only Product Management should add a user story to the backlog or close a user story.

Verification Failed (Internal Use Only)
Marks an issue that the Test team has tested and has failed the criteria. The issue is returned to the Development team.

Verification Passed (Internal Use Only)
Marks an issue that the Test team has tested and has passed the criteria

VS 2012
Marks a Microsoft Visual Studio 2012 issue

VS 2013
Marks a Microsoft Visual Studio 2013 issue