action #34138: [functional][u][epic][eternal] work on any issue from http://github.com/os-autoinst/openqa_review/issues/
[functional][y][medium] Handle "boo#0" not as error in log but better in openqa_review
During retrospective we have identified an issue that boo#0 is used in o3 for some issues and we, as QSF don't see issues labeled with boo#0, which may hide some bugs and/or test issues.
Idea is to improve openqa_review script, which is executed as a cron job against o3 to identify those issues and review them.
- AC1: boo#0 is not reported as error in the log but handled appropriately in the report
Adapt ttm in a way to do what openSUSE RMs need so that no one would use this bugref anymore.
If above not possible workaround in openqa_review by accepting the bugref as special
openSUSE RMs are using the invalid boo#0 bug reference to fool ttm which demands a ticket reference for each failure.
ERROR:openqa_review.openqa_review:Error retrieving details for bugref boo#0 (https://bugzilla.opensuse.org/show_bug.cgi?id=0): 'NoneType' object has no attribute 'getitem'