Project

General

Profile

action #10188

action #10148: better notification and user feedback

[tools][dashboard]Tracking open bugs based on product

Added by dgutu over 4 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Feature requests
Target version:
Start date:
2016-01-12
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Will be very good if we can have sort of list of open bugs on the
product page.
This will save a lot of time by asking people if the bug is open or I need to open one?
This will save some time on searching in bugzilla also...

If I found that a test is failing I can open a bug in put somewhere the link from this bug
so every other person can be sure that bug is present in the link is there.

Please let me know your opinions.
Thank you.


Related issues

Related to openQA Project - action #12092: [tools][dashboard][Feature] - make openQA show when a bug is marked as "RESOLVED FIXED" but still in the productResolved2017-11-18

Related to openQA Project - action #13812: [epic][dashboard] openQA Dashboard ideasNew2017-01-10

History

#1 Updated by coolo over 4 years ago

  • Category changed from 124 to 140

#2 Updated by coolo over 4 years ago

what's wrong with putting it in the comments?

#3 Updated by dgutu over 4 years ago

It could be useful to have this comment/links to bugs here, in build overview
https://openqa.suse.de/tests/overview?distri=sle&version=12-SP2&build=0373&groupid=25

Comments are fine but you need to click on build number, test and go between this
a lot of times to understand if the bug is present for this failed test or not.

Thx.

#4 Updated by coolo over 4 years ago

this page is full. you could have your list in a popup, but that would serve the same value than the comment in the job group. And the link to the job group should be present on all pages.

#5 Updated by okurz over 4 years ago

dgutu I support your ideas. I am thinking about other views rather than adding content on existing pages. Using comments section is just not working, especially without a edit option. We should also consider different views for different use cases.

#6 Updated by dzedro over 4 years ago

I did also think about some place to find openQA bugs, some simple list with useful columns like bug number/description/openQA link/creation date or whatever e.g. https://etherpad.nue.suse.com/p/openQA_bugs

#7 Updated by okurz over 4 years ago

wow, I came up with a pretty similar idea on the weekend, see https://etherpad.nue.suse.com/p/openqa-SLE-review :-)

Your idea of putting up bugs is a good idea but can we structure them as "new", "existing" and such?

#8 Updated by okurz over 4 years ago

  • Parent task set to #10148

this is related to #10148 and also #10212. For easier tracking of bugs that have been opened as the error has been confirmed in openqa, what do you think about using the "whiteboard" in bugs. It is already used to reference "ibs/obs" SR and the automatic notifications. We could add something to the whiteboard and then search for "whiteboard:'openqa:openqa.suse.de'" e.g. https://bugzilla.suse.com/buglist.cgi?quicksearch=whiteboard%3A%27openqa%3Aopenqa.suse.de%27&list_id=3095342 and "whiteboard:'openqa:openqa.opensuse.org'"

proposed format for whiteboard tag:

openqa:<instance>[:<test>[:<state>]]
  • '[…]' marks optional
  • '<…>' encloses a variable to be replaced: ** <instance>: the openqa instance on which this error has been found, e.g. 'openqa.suse.de' ** <test>: test number on openqa instance where the error was (first) found, e.g. last part from URL https://openqa.suse.de/tests/180205 ** <state>: state or state change of the test, e.g. 'failed', 'fixed', 'still_failing', 'stable', 'soft_failed'

Multiple tags are allowed.

Example:

  • Initial failing test: openqa:openqa.suse.de:12345:failed
  • Still failing in next build: former + openqa:openqa.suse.de:12523:still_failing
  • Fixed in next build after that: former + openqa:openqa.suse.de:14389:fixed

Search requests like these should work

https://bugzilla.suse.com/buglist.cgi?quicksearch=whiteboard%3A%22openqa%3Aopenqa.suse.de%22%20AND%20whiteboard%3A%22fixed%22

#9 Updated by okurz over 4 years ago

management has to discuss and decide about whiteboard usage. Management was not asked yet.

Coming up with a list of all open bugzilla bugs which have "something to do with" openqa is actually easy, e.g. for internal openqa instance use
https://bugzilla.suse.com/buglist.cgi?quicksearch=openqa.suse.de

to combine it with a product, e.g. every open bug mentioning our openqa for product "SLES 12 SP1":
https://bugzilla.suse.com/buglist.cgi?quicksearch=openqa.suse.de%20product%3A%22SUSE%20Linux%20Enterprise%20Server%2012%20SP1%22

above but only "RESOLVED" ones, i.e. the ones that should be verified:
https://bugzilla.suse.com/buglist.cgi?quicksearch=openqa.suse.de%20product%3A%22SUSE%20Linux%20Enterprise%20Server%2012%20SP1%22%20status%3ARESOLVED

or add the name of a "test_module" in the query although this could be incomplete, e.g. if people only provide a full URL to the test, not the failed test module:
https://bugzilla.suse.com/buglist.cgi?quicksearch=status%3ARESOLVED%20openqa.suse.de%20AND%20bootloader_s390%20product%3A%22SUSE%20Linux%20Enterprise%20Server%2012%20SP1%22

#10 Updated by dheidler about 4 years ago

The https://github.com/okurz/openqa_review script is now able to query the status of bugzilla and progress issues and include it in the output markdown.

See openqa_review.py --query-issue-status-help for further info.

#11 Updated by okurz about 4 years ago

  • Related to action #12092: [tools][dashboard][Feature] - make openQA show when a bug is marked as "RESOLVED FIXED" but still in the product added

#13 Updated by dheidler about 4 years ago

  • Status changed from New to In Progress
  • Assignee set to dheidler

#14 Updated by okurz about 4 years ago

  • Related to action #13812: [epic][dashboard] openQA Dashboard ideas added

#15 Updated by RBrownSUSE over 3 years ago

  • Subject changed from Tracking open bugs based on product to [tools]Tracking open bugs based on product

#16 Updated by RBrownSUSE over 3 years ago

  • Subject changed from [tools]Tracking open bugs based on product to [tools][dashboard]Tracking open bugs based on product

#17 Updated by coolo almost 3 years ago

  • Status changed from In Progress to Resolved

We track bugs now good enough IMO

#18 Updated by okurz over 2 years ago

  • Target version changed from future to future

Also available in: Atom PDF