https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842019-06-18T11:01:26ZopenSUSE Project Management ToolopenQA Project - action #53264: Show actual "version" in job groups for builds when configured + multiple versions are availablehttps://progress.opensuse.org/issues/53264?journal_id=2213242019-06-18T11:01:26Zhennevogelhvogel@suse.com
<ul></ul><p>Or to group the builds by version under a headline.</p>
openQA Project - action #53264: Show actual "version" in job groups for builds when configured + multiple versions are availablehttps://progress.opensuse.org/issues/53264?journal_id=2213722019-06-18T12:20:44Zmkittlermarius.kittler@suse.com
<ul></ul><p>We use the version already to sort anyways. This sounds easy to implement: The template rendering could simply generate a new headline as soon as the current version of the next bullet point changes.</p>
<p>Note that the index page uses is rendered by the same code. Should it also be affected? Should we hide the version if there is only one version?</p>
openQA Project - action #53264: Show actual "version" in job groups for builds when configured + multiple versions are availablehttps://progress.opensuse.org/issues/53264?journal_id=2214472019-06-18T14:19:00Zokurzokurz@suse.com
<ul><li><strong>Subject</strong> changed from <i>Show actual "version" in job groups for builds when multiple versions are available</i> to <i>Show actual "version" in job groups for builds when configured + multiple versions are available</i></li></ul><p>yes, I also think it's easy as we have the version readily available.</p>
<ul>
<li>index page: yes, should behave the same</li>
<li>headline: either that or version+prefix, both should be fine</li>
<li>hide version: yes, but might be configurable</li>
</ul>
<p>I would still recommend to have an option that decides that, same as we have for group order preferences. If that makes it hard to influence the index page then apply to the job group only</p>
openQA Project - action #53264: Show actual "version" in job groups for builds when configured + multiple versions are availablehttps://progress.opensuse.org/issues/53264?journal_id=3151752020-07-28T11:30:46Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> set to <i>future</i></li></ul> openQA Project - action #53264: Show actual "version" in job groups for builds when configured + multiple versions are availablehttps://progress.opensuse.org/issues/53264?journal_id=4707122021-12-06T16:10:26Zokurzokurz@suse.com
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-4 status-6 priority-4 priority-default closed" href="/issues/103557">action #103557</a>: Aggregate different versions into the same build openqa in group_overview pages</i> added</li></ul> openQA Project - action #53264: Show actual "version" in job groups for builds when configured + multiple versions are availablehttps://progress.opensuse.org/issues/53264?journal_id=4707152021-12-06T16:11:21Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/470715/diff?detail_id=445293">diff</a>)</li></ul> openQA Project - action #53264: Show actual "version" in job groups for builds when configured + multiple versions are availablehttps://progress.opensuse.org/issues/53264?journal_id=4775582022-01-05T08:20:52Zmgrifalconi
<ul><li><strong>Priority</strong> changed from <i>Low</i> to <i>Normal</i></li></ul><p>I would rather prefer to have the <strong>build number aggregated</strong> (see only one entry per day) and have that link point to the aggregate view and not adding info to multiple build numbers and service packs versions.</p>
<p>Example of bad view <a href="https://openqa.suse.de/group_overview/405" class="external">https://openqa.suse.de/group_overview/405</a><br>
What I would like the only build number per day to point to: <a href="https://openqa.suse.de/tests/overview?groupid=405" class="external">https://openqa.suse.de/tests/overview?groupid=405</a></p>
<p><a class="user active user-mention" href="https://progress.opensuse.org/users/28348">@jctmichel</a> also expressed the same preference during the QE Sync meeting on 05-01-2022</p>
<p>I would also raise the priority since this is impacting the usage of this new refactoring and more squads will suffer from it as the refactoring continues.</p>
openQA Project - action #53264: Show actual "version" in job groups for builds when configured + multiple versions are availablehttps://progress.opensuse.org/issues/53264?journal_id=4796102022-01-12T07:58:23Zokurzokurz@suse.com
<ul></ul><p>I guess your approach is a valid alternative. I can see the use case in both. We might need to make that configurable.</p>
openQA Project - action #53264: Show actual "version" in job groups for builds when configured + multiple versions are availablehttps://progress.opensuse.org/issues/53264?journal_id=4796162022-01-12T08:00:20Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/479616/diff?detail_id=454005">diff</a>)</li></ul> openQA Project - action #53264: Show actual "version" in job groups for builds when configured + multiple versions are availablehttps://progress.opensuse.org/issues/53264?journal_id=4804572022-01-17T07:32:46Zmgrifalconi
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul><p>The adoption of the new job group format is increasing and with it the pain caused by the missing aggregate build view requested in comment <a class="issue tracker-4 status-5 priority-4 priority-default closed parent behind-schedule" title="action: Order Promo DVDs (Closed)" href="https://progress.opensuse.org/issues/7">#7</a></p>
<p>Therefore, I propose to increase priority.</p>
<p>More feedback from qac <a href="https://suse.slack.com/archives/C02CGKBCGT1/p1642365943011100" class="external">https://suse.slack.com/archives/C02CGKBCGT1/p1642365943011100</a><br>
QE-Core will adopt this format during this week as well.</p>
openQA Project - action #53264: Show actual "version" in job groups for builds when configured + multiple versions are availablehttps://progress.opensuse.org/issues/53264?journal_id=4814532022-01-19T10:55:01Zokurzokurz@suse.com
<ul><li><strong>Priority</strong> changed from <i>High</i> to <i>Normal</i></li><li><strong>Target version</strong> changed from <i>future</i> to <i>Ready</i></li></ul><p>Based on the above comments and discussion in weekly QE sync 2022-01-19 adding to backlog.</p>
openQA Project - action #53264: Show actual "version" in job groups for builds when configured + multiple versions are availablehttps://progress.opensuse.org/issues/53264?journal_id=4815132022-01-19T12:14:02Zjlausuchjalausuch@suse.com
<ul><li><strong>File</strong> <a href="/attachments/12412">wicked_view.png</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/12412/wicked_view.png">wicked_view.png</a> added</li></ul><p>Maybe it's for another bigger ticket, but if I may suggest something, it would be nice that same build numbers are grouped together.<br>
So, instead of having different entries for the same build (as you can see in the image)<br>
<img src="https://progress.opensuse.org/attachments/download/12412/wicked_view.png" alt="" loading="lazy" /></p>
<p>would be good to have a single row with the build number, and then when clicking and going into the job list view, grouping them by version, the same view when using a url query like this: <code>groupid=X&groupid=Y&groupid=Z</code>.</p>
openQA Project - action #53264: Show actual "version" in job groups for builds when configured + multiple versions are availablehttps://progress.opensuse.org/issues/53264?journal_id=4815222022-01-19T12:24:47Zokurzokurz@suse.com
<ul></ul><p><a class="user active user-mention" href="https://progress.opensuse.org/users/25856">@jlausuch</a> I suggest that we first focus on the easier step to just include the version in the build displayed. After that we can look into multiple additional but also more advanced use cases</p>
openQA Project - action #53264: Show actual "version" in job groups for builds when configured + multiple versions are availablehttps://progress.opensuse.org/issues/53264?journal_id=4816242022-01-19T13:58:45Zmkittlermarius.kittler@suse.com
<ul><li><strong>Assignee</strong> set to <i>mkittler</i></li></ul> openQA Project - action #53264: Show actual "version" in job groups for builds when configured + multiple versions are availablehttps://progress.opensuse.org/issues/53264?journal_id=4816662022-01-19T15:24:14Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul><p>PR: <a href="https://github.com/os-autoinst/openQA/pull/4462" class="external">https://github.com/os-autoinst/openQA/pull/4462</a></p>
<p>This is only about prefixing the version if it was otherwise ambiguous. That should fulfill AC1.</p>
<p>Grouping these as suggested in comments would be a little bit more work and we should define how that should work exactly. Are additional headings for each version enough or should there be a bullet point per version which is expandable to reveal the progress bars per build only when needed? The latter would be a little bit more work to implement, e.g. I suppose on "version level" the figures shown in progress bars needed to be accumulated similar to how it works already for parent groups. That brings me to the next question: Should this work for parent groups? If yes, I suppose that would mean two levels of grouping.</p>
openQA Project - action #53264: Show actual "version" in job groups for builds when configured + multiple versions are availablehttps://progress.opensuse.org/issues/53264?journal_id=4818762022-01-20T09:02:34Zokurzokurz@suse.com
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-4 status-6 priority-3 priority-lowest closed" href="/issues/105118">action #105118</a>: Combine builds for multiple versions depending on configuration</i> added</li></ul> openQA Project - action #53264: Show actual "version" in job groups for builds when configured + multiple versions are availablehttps://progress.opensuse.org/issues/53264?journal_id=4818822022-01-20T09:03:31Zokurzokurz@suse.com
<ul><li><strong>Due date</strong> set to <i>2022-02-02</i></li></ul><p>Let's continue brainstorming about combining multi-version builds in <a class="issue tracker-4 status-6 priority-3 priority-lowest closed" title="action: Combine builds for multiple versions depending on configuration (Rejected)" href="https://progress.opensuse.org/issues/105118">#105118</a> . Here we should focus on the original idea and what you have covered with the PR.</p>
openQA Project - action #53264: Show actual "version" in job groups for builds when configured + multiple versions are availablehttps://progress.opensuse.org/issues/53264?journal_id=4831332022-01-24T10:45:35Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>PR has been merged and deployed on OSD. On <a href="https://openqa.suse.de/group_overview/412" class="external">https://openqa.suse.de/group_overview/412</a> it is working so AC1 is fullfilled.</p>