Goals
The Support SIG 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 in order that they be released in hotfixes
- 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 ....
- PO, or Developer creates a bug in JIRA
- Using the Team Vs Module Matrix assign the appropriate Dev Team (to the best of your understanding)
- Add the "Support' label
- Add the Affected institution - section of Jira
- If the issue is urgent the reporter should
- tag the relevant PO in the issue comments. If user is unable to determine the correct PO, then tag the FOLIO Lead PO
- Assign a "PI" priority - which notifies the Support SIG
- 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" label to the existing JIRA and for each institution that is impacted add them to the: Affected institution - section of Jira.
- If the issue is urgent the reporter should
- Assign a "PI" priority - which notifies the Support SIG