Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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
  • 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. 

...

    • . 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

...