https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842016-01-12T12:22:46ZopenSUSE Project Management ToolopenQA Project - action #10188: [tools][dashboard]Tracking open bugs based on producthttps://progress.opensuse.org/issues/10188?journal_id=201322016-01-12T12:22:46Zcoolocoolo@suse.com
<ul><li><strong>Category</strong> changed from <i>124</i> to <i>140</i></li></ul> openQA Project - action #10188: [tools][dashboard]Tracking open bugs based on producthttps://progress.opensuse.org/issues/10188?journal_id=201342016-01-12T12:24:20Zcoolocoolo@suse.com
<ul></ul><p>what's wrong with putting it in the comments?</p>
openQA Project - action #10188: [tools][dashboard]Tracking open bugs based on producthttps://progress.opensuse.org/issues/10188?journal_id=201382016-01-12T12:38:11Zdgutudgutu@suse.com
<ul></ul><p>It could be useful to have this comment/links to bugs here, in build overview<br>
<a href="https://openqa.suse.de/tests/overview?distri=sle&version=12-SP2&build=0373&groupid=25" class="external">https://openqa.suse.de/tests/overview?distri=sle&version=12-SP2&build=0373&groupid=25</a></p>
<p>Comments are fine but you need to click on build number, test and go between this<br>
a lot of times to understand if the bug is present for this failed test or not.</p>
<p>Thx.</p>
openQA Project - action #10188: [tools][dashboard]Tracking open bugs based on producthttps://progress.opensuse.org/issues/10188?journal_id=201402016-01-12T13:20:05Zcoolocoolo@suse.com
<ul></ul><p>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.</p>
openQA Project - action #10188: [tools][dashboard]Tracking open bugs based on producthttps://progress.opensuse.org/issues/10188?journal_id=201482016-01-12T14:35:59Zokurzokurz@suse.com
<ul></ul><p>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.</p>
openQA Project - action #10188: [tools][dashboard]Tracking open bugs based on producthttps://progress.opensuse.org/issues/10188?journal_id=201542016-01-12T15:55:35Zdzedrojpupava@suse.com
<ul></ul><p>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. <a href="https://etherpad.nue.suse.com/p/openQA_bugs" class="external">https://etherpad.nue.suse.com/p/openQA_bugs</a></p>
openQA Project - action #10188: [tools][dashboard]Tracking open bugs based on producthttps://progress.opensuse.org/issues/10188?journal_id=201562016-01-12T16:07:44Zokurzokurz@suse.com
<ul></ul><p>wow, I came up with a pretty similar idea on the weekend, see <a href="https://etherpad.nue.suse.com/p/openqa-SLE-review" class="external">https://etherpad.nue.suse.com/p/openqa-SLE-review</a> :-)</p>
<p>Your idea of putting up bugs is a good idea but can we structure them as "new", "existing" and such?</p>
openQA Project - action #10188: [tools][dashboard]Tracking open bugs based on producthttps://progress.opensuse.org/issues/10188?journal_id=202462016-01-15T12:23:58Zokurzokurz@suse.com
<ul><li><strong>Parent task</strong> set to <i>#10148</i></li></ul><p>this is related to <a class="issue tracker-4 status-3 priority-4 priority-default closed parent" title="action: better notification and user feedback (Resolved)" href="https://progress.opensuse.org/issues/10148">#10148</a> and also <a class="issue tracker-4 status-3 priority-5 priority-high3 closed child" title="action: labels and badges for builds (Resolved)" href="https://progress.opensuse.org/issues/10212">#10212</a>. 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. <a href="https://bugzilla.suse.com/buglist.cgi?quicksearch=whiteboard%3A%27openqa%3Aopenqa.suse.de%27&list_id=3095342" class="external">https://bugzilla.suse.com/buglist.cgi?quicksearch=whiteboard%3A%27openqa%3Aopenqa.suse.de%27&list_id=3095342</a> and "whiteboard:'openqa:openqa.opensuse.org'"</p>
<p>proposed format for whiteboard tag:</p>
<pre><code>openqa:<instance>[:<test>[:<state>]]
</code></pre>
<ul>
<li>'[…]' marks optional</li>
<li>'<…>' encloses a variable to be replaced:
** <code><instance></code>: the openqa instance on which this error has been found, e.g. 'openqa.suse.de'
** <code><test></code>: test number on openqa instance where the error was (first) found, e.g. last part from URL <a href="https://openqa.suse.de/tests/180205" class="external">https://openqa.suse.de/tests/180205</a>
** <code><state></code>: state or state change of the test, e.g. 'failed', 'fixed', 'still_failing', 'stable', 'soft_failed'</li>
</ul>
<p>Multiple tags are allowed.</p>
<p>Example:</p>
<ul>
<li>Initial failing test: <code>openqa:openqa.suse.de:12345:failed</code></li>
<li>Still failing in next build: former + <code>openqa:openqa.suse.de:12523:still_failing</code></li>
<li>Fixed in next build after that: former + <code>openqa:openqa.suse.de:14389:fixed</code></li>
</ul>
<p>Search requests like these should work</p>
<pre><code>https://bugzilla.suse.com/buglist.cgi?quicksearch=whiteboard%3A%22openqa%3Aopenqa.suse.de%22%20AND%20whiteboard%3A%22fixed%22
</code></pre> openQA Project - action #10188: [tools][dashboard]Tracking open bugs based on producthttps://progress.opensuse.org/issues/10188?journal_id=205142016-01-18T09:53:15Zokurzokurz@suse.com
<ul></ul><p>management has to discuss and decide about whiteboard usage. Management was not asked yet.</p>
<p>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<br>
<a href="https://bugzilla.suse.com/buglist.cgi?quicksearch=openqa.suse.de" class="external">https://bugzilla.suse.com/buglist.cgi?quicksearch=openqa.suse.de</a></p>
<p>to combine it with a product, e.g. every open bug mentioning our openqa for product "SLES 12 SP1":<br>
<a href="https://bugzilla.suse.com/buglist.cgi?quicksearch=openqa.suse.de%20product%3A%22SUSE%20Linux%20Enterprise%20Server%2012%20SP1%22" class="external">https://bugzilla.suse.com/buglist.cgi?quicksearch=openqa.suse.de%20product%3A%22SUSE%20Linux%20Enterprise%20Server%2012%20SP1%22</a></p>
<p>above but only "RESOLVED" ones, i.e. the ones that should be verified:<br>
<a href="https://bugzilla.suse.com/buglist.cgi?quicksearch=openqa.suse.de%20product%3A%22SUSE%20Linux%20Enterprise%20Server%2012%20SP1%22%20status%3ARESOLVED" class="external">https://bugzilla.suse.com/buglist.cgi?quicksearch=openqa.suse.de%20product%3A%22SUSE%20Linux%20Enterprise%20Server%2012%20SP1%22%20status%3ARESOLVED</a></p>
<p>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:<br>
<a href="https://bugzilla.suse.com/buglist.cgi?quicksearch=status%3ARESOLVED%20openqa.suse.de%20AND%20bootloader_s390%20product%3A%22SUSE%20Linux%20Enterprise%20Server%2012%20SP1%22" class="external">https://bugzilla.suse.com/buglist.cgi?quicksearch=status%3ARESOLVED%20openqa.suse.de%20AND%20bootloader_s390%20product%3A%22SUSE%20Linux%20Enterprise%20Server%2012%20SP1%22</a></p>
openQA Project - action #10188: [tools][dashboard]Tracking open bugs based on producthttps://progress.opensuse.org/issues/10188?journal_id=283942016-09-12T12:49:29Zdheidlerdheidler@suse.com
<ul></ul><p>The <a href="https://github.com/okurz/openqa_review" class="external">https://github.com/okurz/openqa_review</a> script is now able to query the status of bugzilla and progress issues and include it in the output markdown.</p>
<p>See <code>openqa_review.py --query-issue-status-help</code> for further info.</p>
openQA Project - action #10188: [tools][dashboard]Tracking open bugs based on producthttps://progress.opensuse.org/issues/10188?journal_id=284902016-09-13T14:16:27Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-3 priority-5 priority-high3 closed parent" href="/issues/12092">action #12092</a>: [tools][dashboard][Feature] - make openQA show when a bug is marked as "RESOLVED FIXED" but still in the product</i> added</li></ul> openQA Project - action #10188: [tools][dashboard]Tracking open bugs based on producthttps://progress.opensuse.org/issues/10188?journal_id=287282016-09-16T11:33:59Zdheidlerdheidler@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Assignee</strong> set to <i>dheidler</i></li></ul> openQA Project - action #10188: [tools][dashboard]Tracking open bugs based on producthttps://progress.opensuse.org/issues/10188?journal_id=289342016-09-19T20:58:26Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-6 status-1 priority-3 priority-lowest parent" href="/issues/13812">coordination #13812</a>: [epic][dashboard] openQA Dashboard ideas</i> added</li></ul> openQA Project - action #10188: [tools][dashboard]Tracking open bugs based on producthttps://progress.opensuse.org/issues/10188?journal_id=437842017-03-14T11:05:17ZRBrownSUSErbrown@suse.com
<ul><li><strong>Subject</strong> changed from <i>Tracking open bugs based on product</i> to <i>[tools]Tracking open bugs based on product</i></li></ul> openQA Project - action #10188: [tools][dashboard]Tracking open bugs based on producthttps://progress.opensuse.org/issues/10188?journal_id=452282017-03-27T15:59:22ZRBrownSUSErbrown@suse.com
<ul><li><strong>Subject</strong> changed from <i>[tools]Tracking open bugs based on product</i> to <i>[tools][dashboard]Tracking open bugs based on product</i></li></ul> openQA Project - action #10188: [tools][dashboard]Tracking open bugs based on producthttps://progress.opensuse.org/issues/10188?journal_id=718482017-11-17T10:26:43Zcoolocoolo@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul><p>We track bugs now good enough IMO</p>
openQA Project - action #10188: [tools][dashboard]Tracking open bugs based on producthttps://progress.opensuse.org/issues/10188?journal_id=1296732018-06-15T19:07:39Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> changed from <i>future</i> to <i>future</i></li></ul>