https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842019-03-13T08:23:23ZopenSUSE Project Management Toolqe-yam - coordination #49157: [epic] Introduce yast2_clone to more scenarioshttps://progress.opensuse.org/issues/49157?journal_id=1987492019-03-13T08:23:23Zriafarov
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/198749/diff?detail_id=196898">diff</a>)</li></ul> qe-yam - coordination #49157: [epic] Introduce yast2_clone to more scenarioshttps://progress.opensuse.org/issues/49157?journal_id=1991722019-03-14T10:44:04Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> set to <i>Milestone 24</i></li></ul><p>As we discussed, as this is related to near-always failing autoyast tests and blocking us I think we should work on that soon, e.g. in milestone 24. I will try to find some other tickets to delay for later instead.</p>
qe-yam - coordination #49157: [epic] Introduce yast2_clone to more scenarioshttps://progress.opensuse.org/issues/49157?journal_id=2090332019-04-30T09:08:34Zriafarov
<ul><li><strong>Target version</strong> changed from <i>Milestone 24</i> to <i>Milestone 25</i></li></ul> qe-yam - coordination #49157: [epic] Introduce yast2_clone to more scenarioshttps://progress.opensuse.org/issues/49157?journal_id=2104192019-05-07T08:53:00ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Due date</strong> changed from <i>2019-05-07</i> to <i>2019-05-21</i></li></ul><p>due to changes in a related task</p>
qe-yam - coordination #49157: [epic] Introduce yast2_clone to more scenarioshttps://progress.opensuse.org/issues/49157?journal_id=2135122019-05-21T09:09:24ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Due date</strong> changed from <i>2019-05-21</i> to <i>2019-06-04</i></li></ul><p>due to changes in a related task</p>
qe-yam - coordination #49157: [epic] Introduce yast2_clone to more scenarioshttps://progress.opensuse.org/issues/49157?journal_id=2173912019-06-03T10:40:49Zriafarov
<ul><li><strong>Due date</strong> changed from <i>2019-06-04</i> to <i>2019-07-09</i></li></ul><p>due to changes in a related task</p>
qe-yam - coordination #49157: [epic] Introduce yast2_clone to more scenarioshttps://progress.opensuse.org/issues/49157?journal_id=2206462019-06-14T12:42:01Zriafarov
<ul><li><strong>Target version</strong> changed from <i>Milestone 25</i> to <i>Milestone 27</i></li></ul> qe-yam - coordination #49157: [epic] Introduce yast2_clone to more scenarioshttps://progress.opensuse.org/issues/49157?journal_id=2213362019-06-18T11:07:15Zriafarov
<ul><li><strong>Due date</strong> changed from <i>2019-07-09</i> to <i>2020-01-14</i></li></ul><p>due to changes in a related task</p>
qe-yam - coordination #49157: [epic] Introduce yast2_clone to more scenarioshttps://progress.opensuse.org/issues/49157?journal_id=2437402019-09-16T10:43:54Zmgriessmeiermgriessmeier@suse.com
<ul><li><strong>Target version</strong> changed from <i>Milestone 27</i> to <i>Milestone 28</i></li></ul> qe-yam - coordination #49157: [epic] Introduce yast2_clone to more scenarioshttps://progress.opensuse.org/issues/49157?journal_id=2519362019-10-22T14:20:17Zriafarov
<ul><li><strong>Target version</strong> changed from <i>Milestone 28</i> to <i>future</i></li></ul> qe-yam - coordination #49157: [epic] Introduce yast2_clone to more scenarioshttps://progress.opensuse.org/issues/49157?journal_id=2709982020-01-14T09:42:36Zriafarov
<ul><li><strong>Due date</strong> changed from <i>2020-01-14</i> to <i>2020-01-28</i></li></ul><p>due to changes in a related task</p>
qe-yam - coordination #49157: [epic] Introduce yast2_clone to more scenarioshttps://progress.opensuse.org/issues/49157?journal_id=3339732020-10-12T13:37:29Zszarate
<ul><li><strong>Tracker</strong> changed from <i>action</i> to <i>coordination</i></li></ul> qe-yam - coordination #49157: [epic] Introduce yast2_clone to more scenarioshttps://progress.opensuse.org/issues/49157?journal_id=3348192020-10-12T13:46:39Zszarate
<ul></ul><p>See for the reason of tracker change: <a href="http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html" class="external">http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html</a></p>
qe-yam - coordination #49157: [epic] Introduce yast2_clone to more scenarioshttps://progress.opensuse.org/issues/49157?journal_id=3385332020-10-21T09:27:49Zriafarov
<ul><li><strong>Project</strong> changed from <i>openQA Tests</i> to <i>qe-yam</i></li><li><strong>Subject</strong> changed from <i>[functional][y][epic] Introduce yast2_clone to more scenarios</i> to <i>[epic] Introduce yast2_clone to more scenarios</i></li><li><strong>Category</strong> deleted (<del><i>New test</i></del>)</li><li><strong>Assignee</strong> set to <i>riafarov</i></li></ul> qe-yam - coordination #49157: [epic] Introduce yast2_clone to more scenarioshttps://progress.opensuse.org/issues/49157?journal_id=4045512021-05-06T10:03:22Zriafarov
<ul><li><strong>Assignee</strong> changed from <i>riafarov</i> to <i>oorlov</i></li></ul> qe-yam - coordination #49157: [epic] Introduce yast2_clone to more scenarioshttps://progress.opensuse.org/issues/49157?journal_id=4952412022-02-24T14:35:10Zoorlovoorlov@suse.com
<ul><li><strong>Assignee</strong> changed from <i>oorlov</i> to <i>JERiveraMoya</i></li></ul> qe-yam - coordination #49157: [epic] Introduce yast2_clone to more scenarioshttps://progress.opensuse.org/issues/49157?journal_id=7469692023-12-19T13:55:04ZJERiveraMoyajeriveramoya@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li></ul><p>Enough test coverage in YaST job group.</p>