Skip to end of banner
Go to start of banner

PO and Developers - Bug Reporting and Management Process

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Support Process for when a PO or Developer identifies a bug effecting a Production library ....

  1. PO, or Developer create a bug JIRA
  2. Add the "Support' label
  3. Add the Affected institution - section of Jira


Definitions

  • Bug: Specified functionality does not work
  • Critical Feature:  Implicit functionality does not work. In cases where users would have assumed certain aspects of a feature, but these were not explicitly specified, then the reported bug will be treated as a Critical Feature.  The PO will add the "support label".  The customer priority field for Production libraries should be completed ie : Critical, Important, medium, low  or not indicated.
  • Feature: Functionality that was neither explicitly nor implicitly specifies but that a Production or Implementing library would like.  The "Support" label will not be used. 

Managing Duplicate UXPRODS and Bugs

If a PO wants to close a bug as a duplicate of a UXPROD features, implementers can track it as long as the label says "support" it will still show up on the support dashboard.  POs will consult the production libraries before making the decision. For bugs - each institution that is impacted should be in the : Affected institution - section of Jira.


  • No labels