Feature #7626

version due date and issue due date interactions

Added by James Rowe almost 12 years ago.

Status:NewStart date:2011-02-15
Priority:NormalDue date:
Assignee:-% Done:


Target version:-


When adding issues to versions I expected the due date of the issue to match the due date of the version.

Here are some behaviors I thought would be nice:

  • If an issue without a due date is added to a version with a due date it gets that due date
  • If a due date is changed on a version prompt to 'standardize' this due date for the rest of the issues
  • If an issue due date is changed to after the version due date a warning is thrown(?)

I was expecting similar interactions with due dates as related tickets have with percent done.

Related issues

Related to Redmine - Patch #251: Patch for Feature Request #9785 (Default issues due date ... New
Related to Redmine - Feature #6366: Due date on an issue should follow the associated release... New 2010-09-11
Related to Redmine - Feature #5451: Make Start Date/Due Date settable to versions/milestones New

Also available in: Atom PDF