Project

General

Profile

Actions

action #95536

closed

Due dates on blocked tickets should be reset automatically

Added by livdywan over 3 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
QA (public, currently private due to #173521) - future
Start date:
2021-07-15
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Blocked tickets adopt the due date from related tickets. Generally the solution to handle a ticket that's exceeding its due date but blocked is to remove the due date from it. This shouldn't have to be done manually.

Acceptance criteria

  • AC1: Due dates on blocked tickets require no manual intervention

Suggestions

Actions #1

Updated by okurz over 3 years ago

  • Category set to Feature requests
  • Target version set to Ready
  • Parent task set to #69310

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 #69310 . 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.

Actions #2

Updated by livdywan over 3 years ago

okurz wrote:

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 #69310 . 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.

Right, that sounds like what I meant. Typically our parent epics are blocked so in my head that's the same use case.

Actions #3

Updated by okurz over 3 years ago

so can you rewrite this ticket to express what you mean?

Actions #4

Updated by okurz over 3 years ago

  • Priority changed from Normal to Low
Actions #5

Updated by okurz over 3 years ago

  • Target version changed from Ready to future
Actions #6

Updated by okurz almost 3 years ago

  • Status changed from New to Rejected
  • Assignee set to okurz

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.

Actions

Also available in: Atom PDF