Issue Tracking and Resolution Process - abb-iss/issues GitHub Wiki

We manage identified problems with software, hardware, and process with GitHub issues on this GitHub project https://github.com/abb-iss/issues/issues

Historically, we tracked bugs in Pivotal Tracker; henceforth, all bugs should be reported and tracked only in this GitHub project.

Issue workflow has three phases:

  1. Report a Problem – someone creates a record for the issue in GitHub
  2. Triage – determine the intended way to resolve the issue and who should resolve it
  3. Resolution – describe the resolution and close the issue

Team members who originate issues can progress it through Report the Problem and Triage phases if they wish.

Report the Problem

Once you have identified a problem, proceed with the following:

  1. (Optional) Discuss the problem with an appropriate team member responsible for the thing
  2. Decide whether to create an issue for it (when in doubt report it) on the issues list

Triage

The person responsible for the issue repository will review the issues at least daily and do the following:

  1. Tag the issue with one of the labels starting with p- for the thing that is the source of the issue
  2. Apply any other appropriate label (e.g. β€œbug”)
  3. Check with the originator if there are any unclear aspects of the issue
  4. Discuss the issue with an appropriate team member who could address it and assign it to them once they agree to work on it
  5. Assign a target milestone (if applicable) for the fix
  6. Respond to the originator that the issue has been assigned to a team member for resolution

Resolution

For bug issues that are fixed:

  1. When you commit the fix, reference the issue in GitHub. If the issue is on the public issues list, reference it in your commit message like β€œfixes abb-iss/issues#1” where 1 is whatever issue number you have.
  2. Enter a description of the resolution in the GitHub issues list
  3. After release of the fix to users, update the issue to closed

To close other issues (or close bugs without fixes):

  1. Discuss the resolution status or reason the bug won't be fixed with the originator
  2. Enter a description of the resolution in the GitHub issues list
  3. Add an appropriate label to the issue for status other than fixed:
  • Duplicate – when this is a duplicate of another issue
  • Invalid – when the issue is not a problem or reflects design intent
  • Wontfix – when we decide not to fix the issue

Finally, Close the issue