[tools][dashboard][Feature] - make openQA show when a bug is marked as "RESOLVED FIXED" but still in the product
Idea came on to Richard on openQA hackaton:
Make openQA show when a bug is marked as "RESOLVED FIXED" but still in the product
- The Bug icons on the test result matrix page should indicate the status (open/closed) of the bug
- More detailed status indicator
- Mouseover box with more details about the bug
#1 Updated by dgutu almost 6 years ago
#2 Updated by coolo almost 6 years ago
- Category changed from 124 to 140
this requires openQA to have an understanding what bugs are beside just a string that matches a regexp. But what you describe can (and IMO should) be implemented in the external review script. openQA should provide the info about the currently happing bugs (as in the test review comments) and bugzilla provides the state of it. Having an external tool that combines them and spits out that comment either for a reviewer to read (and possibly fix either side) or for all to read into the group overview.
OBS implements some kind of issue tracker and knowing how many code is required and how many problems we had to solve to get this going I sure would like to see a really good business case on how much time this saves us.
Especially taking that a resolved bug does not mean the next build will not have this problem - RESOLVED means basically nothing to QA, until the bug is gone and should be VERIFIED. So yes, if you care for verifying bugs, you want an enitity to have an overview of all databases. But I disagree that this entity should be openQA.
#5 Updated by okurz over 5 years ago
- Assignee set to dheidler
"openqa_review" can read bugzilla issue status, subject and assignee since https://github.com/okurz/openqa_review/pull/8
https://w3.nue.suse.com/~okurz/openqa_suse_de_status.html shows the status for each bugref (as well as progress issues) so it got pretty easy to track which bugs are RESOLVED FIXED but still in the product.
- Customized reports based on that data, e.g.
- all RESOLVED bugs but tests still fail
- tests that fail but nobody cares about the bugs (e.g. "NEW" bugs for existing product issues)
- bugs without assignees (or no personal assignees, only mailing lists)
#11 Updated by RBrownSUSE about 5 years ago
- % Done changed from 100 to 40
While the openqa-review feature is nice, we really need the icons on the matrix view to also show the status of the bug in bugzilla. Its particually important to identify bugs which Bugzilla reports as closed but are still present in the product - These should probably be flagged with a red bug icon or something similar.
#15 Updated by dheidler almost 5 years ago
- % Done changed from 40 to 90
#18 Updated by dheidler over 4 years ago
For o3 we need to find a solution how to deal with private bugs.
We could report them to o3 as non-existing. But that would result in
a wrong bug status info in the o3 db.
Or we could use a bugzilla account with access to private bugs
and let it return everything. Bug this could leak private data
so I would prefer the 1st solution.
#19 Updated by dheidler over 4 years ago
I created a new bugzilla account (o3bugfetcher) without employ status to fetch o3 bugs.
I updated openqa_bugfetcher so that it will skip the bugs that it can't access.
That means, that it will try to fetch that bugs again at every cron-call.
To avoid it DOSing bugzilla I only run the o3 bugfetcher every 10 hours - not every 10 minutes like osd bugfetcher.