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

Goals

The Support SIG works works with libraries, Product owners and developers to surface bugs effecting libraries that are, or will soon be, in production with the intent of:

  • assuring system functionality
  • surfacing issues that will effect future FOLIO development
  • facilitating prioritization and resolution of P1-P3 level bugs
  • improving specifications
  • improving FOLIO


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. The RCA (root cause analysis) designation of these bugs is "Incomplete requirements"


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
  4. If applicable assign the RCA


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