Closing Jira issues:

  1. QA should close all Jira issues. The exceptions to this are when developers enter work notes for themselves or notes for website/project work that are separate from the Thalia application.
    Note: Developers should consider if issues they're creating are notes for obvious changes that need to be done vs. changes that are wanted but not approved/know to team. Issues that are requesting a change to functionality should be put in Triage for team review.
  2. Comments should be added when closing issues to answer questions for others reading later. Comments should follow this format:
    "Closing, verified by (describe at high level some of the testing, other areas checked, etc.), build version, URL where tested, operating system, user level (non-admin, admin or guest)."
  3. Issues not fully resolved that need discussion should be Reopened with the Fixed Release changed to Triage for discussion at next Triage meeting.
  4. Issues mostly resolved should be Closed with a new issue created to cover the outstanding part, and then Link the issues.
  • No labels