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 6 Next »

Definitions

  • Bug: Specified functionality does not work as defined in User Story by Product Owner
  • Spec Bug:  Functionality does not work as assumed, but developers have delivered what the Product Owner defined in the User Story
  • 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 specified but that a Production or Implementing library would like.  The "Support" label will not be used. 


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

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


Support Process for when a PO or Developer identifies a bug JIRA as a duplicate UXPROD

If a PO wants to close a bug as a duplicate of a UXPROD features they will add the "support" to the JIRA and  for each institution that is impacted add them to the: Affected institution - section of Jira.


  • No labels