/
FSA Guidelines
FSA Guidelines
Additional checks for a Bug
- Consider cherry-pick for previous release(s)
- Add Jira reference to relevant section in read the docs (RTD) ('Bug Fixes' and possibly 'Security Notes'). The slogan does NOT have to be identical to the Jira, it often could/should be a better description of the change
Complete an Fault Slip-through Analysis (FSA) and add as a comment in Jira
Agree with Customer the FSA especially if there are any follow-up actions needed BEFORE closing the bug
FSA analysis is an ongoing process so other individuals will be reviewing these JIRAs. Please ensure you answer fields in such a manner as to enable others to understand easily without having to read all comments in the Jira ticket
Related content
Bug Reporting Guidelines for CPS
Bug Reporting Guidelines for CPS
Read with this
CPS Definition of Done (and FSA)
CPS Definition of Done (and FSA)
More like this
Configuration Persistence Service Developer's Landing Page
Configuration Persistence Service Developer's Landing Page
Read with this
CPS-2055: Improve WoWs around Bug tickets
CPS-2055: Improve WoWs around Bug tickets
More like this
Tracking Issues with JIRA
Tracking Issues with JIRA
More like this
Communication Templates
Communication Templates
More like this