https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842021-07-16T07:25:40ZopenSUSE Project Management ToolopenQA Project - action #95536: Due dates on blocked tickets should be reset automaticallyhttps://progress.opensuse.org/issues/95536?journal_id=4278462021-07-16T07:25:40Zokurzokurz@suse.com
<ul><li><strong>Category</strong> set to <i>Feature requests</i></li><li><strong>Target version</strong> set to <i>Ready</i></li><li><strong>Parent task</strong> set to <i>#69310</i></li></ul><p>I think you are mixing up something here. Blocked tickets do not automatically inherit any due-date. Rather, parent tasks do from subtasks. This is the idea I described now in <a class="issue tracker-6 status-3 priority-4 priority-default closed parent" title="coordination: [epic] SUSE QA tools team ticket process helpers (Resolved)" href="https://progress.opensuse.org/issues/69310">#69310</a> . And for blocked tickets I think due-dates still make sense, only in a different sense: Rather than an expectation when we can really be finished a due-date on blocked ticket can act as reminder when at the latest to check for the status in the blocker ticket and remind to fix the blocker.</p>
openQA Project - action #95536: Due dates on blocked tickets should be reset automaticallyhttps://progress.opensuse.org/issues/95536?journal_id=4279572021-07-16T12:38:45Zlivdywanliv.dywan@suse.com
<ul></ul><p>okurz wrote:</p>
<blockquote>
<p>I think you are mixing up something here. Blocked tickets do not automatically inherit any due-date. Rather, parent tasks do from subtasks. This is the idea I described now in <a class="issue tracker-6 status-3 priority-4 priority-default closed parent" title="coordination: [epic] SUSE QA tools team ticket process helpers (Resolved)" href="https://progress.opensuse.org/issues/69310">#69310</a> . And for blocked tickets I think due-dates still make sense, only in a different sense: Rather than an expectation when we can really be finished a due-date on blocked ticket can act as reminder when at the latest to check for the status in the blocker ticket and remind to fix the blocker.</p>
</blockquote>
<p>Right, that sounds like what I meant. Typically our parent epics are blocked so in my head that's the same use case.</p>
openQA Project - action #95536: Due dates on blocked tickets should be reset automaticallyhttps://progress.opensuse.org/issues/95536?journal_id=4280322021-07-16T18:05:17Zokurzokurz@suse.com
<ul></ul><p>so can you rewrite this ticket to express what you mean?</p>
openQA Project - action #95536: Due dates on blocked tickets should be reset automaticallyhttps://progress.opensuse.org/issues/95536?journal_id=4281222021-07-19T06:12:33Zokurzokurz@suse.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul> openQA Project - action #95536: Due dates on blocked tickets should be reset automaticallyhttps://progress.opensuse.org/issues/95536?journal_id=4315132021-07-29T12:02:07Zokurzokurz@suse.com
<ul><li><strong>Target version</strong> changed from <i>Ready</i> to <i>future</i></li></ul> openQA Project - action #95536: Due dates on blocked tickets should be reset automaticallyhttps://progress.opensuse.org/issues/95536?journal_id=4758002021-12-23T10:20:16Zokurzokurz@suse.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li><li><strong>Assignee</strong> set to <i>okurz</i></li></ul><p>By now I think we are fine with no due-date reset. A due-date on blocked tickets can serve as valid reminder to check the blocker itself. And commonly of course we should be ok to update the due-date to a sensible choice as soon as we decide to change a ticket from any other status to blocked.</p>