Tracker bug for OCP 4.6 on Z issues
Adding a "Target Release" before the bug is evaluated by team. The Target Release is initially set to 4.6 because this is a non-blocker and is a 4.6 related bug.
Hi Dan, (In reply to Dan Li from comment #1) > Adding a "Target Release" before the bug is evaluated by team. The Target > Release is initially set to 4.6 because this is a non-blocker and is a 4.6 > related bug. the intention is to use this BZ just as tracker. I am not sure if you already have one (as usual practice on RHEL). At least, I saw a couple of bugs here and there and like to have a tracker to see the entire picture. We probably could improve this on tracking per release or other. Any ideas are welcome.
Thank you for the explanation, Hendrik. That is my understanding as well. By system rule, any 4.6 bug that does not have a target release set is considered to be "untriaged". That was the reason for my change earlier.
OCP bug protocol is different than RHEL's, and doesn't really work with tracker bugs. I think you'll need to use Jira for tracking purposes.
Adding UpcomingSprint label as this is a tracker bug (not an actual bug).
1888754
https://bugzilla.redhat.com/show_bug.cgi?id=1888894
(In reply to Christian LaPolt from comment #6) > 1888754 https://bugzilla.redhat.com/show_bug.cgi?id=1889427 - 4.5.15 unable to update. Still open but appears to be fixed
1. Setting this bug as low priority because it is a tracker bug (not an actual bug) 2. Keeping the assignee as Dennis but changing the status as Assigned. There are no actions to be taken with this bug
Taking this tracker bug from Dennis as I have been coordinating bug triaging with the team.
Setting the "Reviewed-in-Sprint" flag to + as this is a tracker bug (not an actual bug)
Setting "Reviewed-in-Sprint" as this is a tracker bug only (not an actual bug).
All the dependent bugs have been closed so closing this bz.