...
- Consider cherry-pick for previous release(s)
- Add Jira reference to relevant section ('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 teh the bug
Expand title 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>
Expand title FSA Fields and Options - Bug Category:
3PP
Critical Vulnerability
Documentation
Functional
High Availability
Install
Logging
Performance
Robustness
Rollback
Scalability
Security
Testware/CI
- Upgrade
- Reason for Slippage:
- Insufficient test coverage
- Intermittent Fault/Timing Issue
- Missed impact
- Missed in code review
- Missed in design analysis
- Missed in document review
- Missing requirement
- Unrealistic Development timeframe
- Late requirement: insufficient analysis
- Environment
- Action needed to prevent slippage: <free text>
- Phase it should have been found in:
- Design
- Review
- Automated (unit) Test
- Microservice CI (CIST)
- Release
- Category of test it should have been found in:
- Unit
- Integration Test
- Performance
- Description of test it should have been found in: <free text>
- Link(s) To JIRA improvement record: <free text>
(ensure there are linked JIra's for any follow-up/preventive actions)
...