Patch #251

Patch for Feature Request #9785 (Default issues due date == assigned target version date)

Added by Elliot Winkler almost 15 years ago. Updated 9 months ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

This patch makes it so that if a new issue is assigned to a version, but the end date isn't specified, the end date
is automatically filled in with the end date of the version.

(I hope the diff is in the right format, I've never really done this before)

auto_end_date.diff Magnifier (1.89 KB) Elliot Winkler, 2008-02-03 11:02

test.png (141 Bytes) sss sss, 2022-03-10 21:02

test.svg (141 Bytes) sss sss, 2022-03-10 21:02

test.png (161 Bytes) sss sss, 2022-03-10 21:08

test.png (136 Bytes) sss sss, 2022-03-10 21:18

Related issues

Related to Redmine - Feature #6366: Due date on an issue should follow the associated release... New 2010-09-11
Related to Redmine - Feature #7626: version due date and issue due date interactions New 2011-02-15
Related to Redmine - Feature #5451: Make Start Date/Due Date settable to versions/milestones New

History

#1 Updated by Felix Schäfer over 12 years ago

  • Assignee set to Eric Davis

Implemented in Eric's issue due date plugin. Should we get this into core or close this issue in favor of the plugin?

#2 Updated by Eric Davis about 12 years ago

  • Assignee deleted (Eric Davis)

#3 Updated by Mischa The Evil about 11 years ago

  • Subject changed from Patch for Feature Request #9785 (Default end date) to Patch for Feature Request #9785 (Default issues due date == assigned target version date)

For referencing purposes: issue #9785 on historic issue tracker.

#4 Updated by sss sss 9 months ago

#5 Updated by sss sss 9 months ago

#6 Updated by sss sss 9 months ago

Also available in: Atom PDF