-
Sub-task
-
Resolution: Done
-
Undefined
-
None
-
None
-
False
-
None
-
False
-
ACM-633 - RHACM Assembly and Channels for Market Consumption
-
-
Tracking bug fixes and related QE delivered across multiple releases, and how best to do that. We also need a way to surface-up bugs that should be noted in the errata of a particular release.
- Currently in 2.8, teams are required to clone bugs so there’s one for each release. Cloning solves the problem but there may be better approaches that avoid splintering of comments across Jira issues and increased volume of issues on scrum boards.
- Potential Alternatives (not exhaustive):
- Use Target Version to specify where the fix will be made by Engineering. QE would update the Fix Version/s once the fix is verified on a particular release.
- Use Sub-tasks to track activities in a given release (kind of what QE does today for stories?)
- Use some kind of label approach to indicate a bug is verified across multiple streams