https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842018-10-30T13:58:58ZopenSUSE Project Management ToolopenQA Project - action #43112: Enhancement for overview page(s): show blocked in /tests/overview as well; rethink color choice for blockedhttps://progress.opensuse.org/issues/43112?journal_id=1611022018-10-30T13:58:58Zsbehlertbehlert@suse.com
<ul><li><strong>Subject</strong> changed from <i>Enhancement for overview page</i> to <i>Enhancement for overview page(s)</i></li></ul> openQA Project - action #43112: Enhancement for overview page(s): show blocked in /tests/overview as well; rethink color choice for blockedhttps://progress.opensuse.org/issues/43112?journal_id=2220592019-06-20T15:12:54Zokurzokurz@suse.com
<ul><li><strong>Category</strong> set to <i>Feature requests</i></li></ul> openQA Project - action #43112: Enhancement for overview page(s): show blocked in /tests/overview as well; rethink color choice for blockedhttps://progress.opensuse.org/issues/43112?journal_id=2368942019-08-20T20:49:19Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>Enhancement for overview page(s)</i> to <i>Enhancement for overview page(s): show blocked in /tests/overview as well; rethink color choice for blocked</i></li></ul> openQA Project - action #43112: Enhancement for overview page(s): show blocked in /tests/overview as well; rethink color choice for blockedhttps://progress.opensuse.org/issues/43112?journal_id=2369902019-08-21T05:57:20Zcoolocoolo@suse.com
<ul><li><strong>Target version</strong> set to <i>Ready</i></li><li><strong>Difficulty</strong> set to <i>easy</i></li></ul><p>It's actually fairly easy to implement, the job knows what it's blocked_by in the DB. The hardest part is really picking a colour :)</p>
openQA Project - action #43112: Enhancement for overview page(s): show blocked in /tests/overview as well; rethink color choice for blockedhttps://progress.opensuse.org/issues/43112?journal_id=2373112019-08-21T14:48:54Zmkittlermarius.kittler@suse.com
<ul><li><strong>Assignee</strong> set to <i>mkittler</i></li></ul><p>Yes, should be easy to implement. When we change the color (to avoid confusion with errors) I'd say that we should use that color on <code>/tests</code> then as well for consistency.</p>
openQA Project - action #43112: Enhancement for overview page(s): show blocked in /tests/overview as well; rethink color choice for blockedhttps://progress.opensuse.org/issues/43112?journal_id=2373202019-08-21T15:36:00Zmkittlermarius.kittler@suse.com
<ul></ul><p>PR: <a href="https://github.com/os-autoinst/openQA/pull/2276" class="external">https://github.com/os-autoinst/openQA/pull/2276</a></p>
openQA Project - action #43112: Enhancement for overview page(s): show blocked in /tests/overview as well; rethink color choice for blockedhttps://progress.opensuse.org/issues/43112?journal_id=2390542019-08-28T09:20:42Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>PR has been merged</p>
openQA Project - action #43112: Enhancement for overview page(s): show blocked in /tests/overview as well; rethink color choice for blockedhttps://progress.opensuse.org/issues/43112?journal_id=2483962019-10-09T05:49:16Zcoolocoolo@suse.com
<ul><li><strong>Target version</strong> changed from <i>Ready</i> to <i>Done</i></li></ul>