Skip to content
This repository was archived by the owner on Sep 4, 2019. It is now read-only.

Issue process

Jump to bottom
Pam Colquhoun edited this page Mar 6, 2015 · 12 revisions

When you create an issue, there are several steps it may go through including assessment, fixing, testing, verification, and closure. Not all issues require the same steps.

Creating issues

You must be signed in before you can submit an Issue.

Note: To keep all communication related to an issue together, use the comment section of the specific issue.

To create an issue:

  1. In the https://github.com/blackberry/VSPlugin repository, click Issues and then click New Issue.
  2. In the Title field, enter an appropriately descriptive title for the issue.
  3. In the body of the issue give as much detail concerning the defect as possible.
  4. Click Submit new issue.

Minimum requirements that must be provided:

  • Software version of each of the following:
    • BlackBerry Native Plug-in for Microsoft Visual Studio
    • SDK
    • Microsoft Visual Studio
  • Steps required to reproduce the issue
  • Expected behavior
  • Actual behavior
  • User environment (OS version, device type, device OS version)
  • Project files (if possible)

Note: If the minimum requirements are not provided when submitting an issue, the issue is sent back to the issue originator to provide the missing information.

Assessing issues

The development, product, and test teams assess each issue and, based on the assessment, assign the initial priority level (P1, P2, P3). Depending on the priority, the issue may be:

  • Assigned to development for resolution
  • Placed in the backlog for future consideration

If the issue is a duplicate of an existing issue, the duplicate label is applied and the issue is closed. (See Label index)

Fixing and testing issues

The development team works with the test team to verify that the issue is reproducible. If the issue is not reproducible, the not reproducible label is applied and the issue is closed. If the issue is reproducible, the development team codes, completes unit testing, and integrates the fix. (See Test strategy) The test team may be asked to verify the issue. Testing is intended to catch issues that failed verification. When the issue is fixed, a pull request is issued and the fix is merged into the Next branch of code. The issue cannot be marked completed unless it is an official BlackBerry release. (See Branch definitions) A new BlackBerry official release is generated by creating a new installer with the fixed issues included. The included issues are marked with the completed label. When the issue is marked completed, the issue is ready for verification and is assigned to the test team lead.

Verifying and closing issues

The test team receives a new BlackBerry official release build with the issues to be verified marked with the completed label. If an issue fails verification, the issue is labelled verification failed and re-assigned back to the development team. If an issue passes verification, the issue is closed.

An issue is closed for the following reasons:

  • The issue is fixed and verified
  • The issue is recommended for closure. This may be because an issue is a duplicate of an existing issue or there is a user error.
  • The issue is identified as no intent to fix. This may be because there is an issue that the development team and product management have acknowledged, but do not feel is critical enough to fix.

See Tracking issues

Clone this wiki locally