action #139055
Updated by livdywan about 1 year ago
## Observation I was using openqa-advanced-retrigger-jobs to retrigger failed jobs and also include a comment 1. See how https://openqa.suse.de/tests/12753455#comments has a comment `Re-running to verify connection with poo#138698` 2. See how the clone has a takeover message https://openqa.suse.de/tests/12754970#comments 3. See how the build also includes the "bugref" https://openqa.suse.de/tests/overview?groupid=439&distri=sle&version=15-SP4&build=%3A31277%3Apostgresql As far as I was aware bugs/tickets/issues must be separate or they won't be treated as bugrefs. I'm not sure if this is a regression. It caught me by surprise at the least. ## Acceptance criteria * **AC1:** It is clear from the docs how bugref semantics work ## Suggestions * Confirm if this behavior is a regression * Add documentation to clarify the behavior - it seems like we don't have any specific examples that would help find out if this was expected or not * Decide if this is desirable or not, and change the code accordingly * Consider #136244 which is also discussing the semantics of bugrefs