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 Comment Template
Fault Slip Through Analysis
- Bug Category: <choose option>
- Reason for Slippage: <choose option>
- Action needed to prevent slippage: <free text>
- Phase it should have been found in: <choose option>
- Category of test it should have been found in: <choose option>
- Description of test it should have been found in: <free text>
- Link(s) To JIRA improvement record: <free text>
FSA Fields and Options
1. Bug Category:
  1. 3PP
  2. Critical Vulnerability
  3. Documentation
  4. Functional
  5. High Availability
  6. Install
  7. Logging
  8. Performance
  9. Robustness
  10. Rollback
  11. Scalability
  12. Security
  13. Testware/CI
  14. Upgrade
2. Reason for Slippage:
  1. Insufficient test coverage
  2. Intermittent Fault/Timing Issue
  3. Missed impact
  4. Missed in code review
  5. Missed in design analysis
  6. Missed in document review
  7. Missing requirement
  8. Unrealistic Development timeframe
  9. Late requirement: insufficient analysis
  10. Environment
3. Action needed to prevent slippage: <free text>
4. Phase it should have been found in:
  1. Design
  2. Review
  3. Automated (unit) Test
  4. Microservice CI (CIST)
  5. Release
5. Category of test it should have been found in:
  1. Unit
  2. Integration Test
  3. Performance
6. Description of test it should have been found in: <free text>
7. Link(s) To JIRA improvement record: <free text>
  (ensure there are linked JIra's for any follow-up/preventive actions)
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

Browser not supported