Project

General

Profile

Actions

Feature #1505

closed

Default an issue's due date to the assigned version's due date [Includes Patch]

Added by Brian Terlson almost 16 years ago. Updated over 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
2008-06-19
Due date:
% Done:

0%

Estimated time:
Resolution:
Wont fix

Description

I wasn't sure where to go with this one, as I've included a patch with a possible implementation, but it's more of a feature request as I'm not sure all aspects of this feature are desirable.

It seems to me that when an issue is assigned to a specific version and that version has a due date and that due date is out in the future at some point, the issue's due date should naturally default to when the specified version is due. Makes sense to me, at least.

I've attached two patches, one puts the functionality in the controller (less good), the other puts it in the Issue model's before_create callback (better).

Now, this could be more robust and check to see if the target version ever changes, and if it does apply the default. If that's the wish I could whip something like that up too - perhaps by utilizing the same sort of code found in Issue's before_save callback.


Files

default_due_date.diff (1.24 KB) default_due_date.diff Functionality in controller Brian Terlson, 2008-06-19 21:52
default_due_date_model.diff (552 Bytes) default_due_date_model.diff Functionality in model callback Brian Terlson, 2008-06-19 21:52

Related issues

Related to Redmine - Patch #777: Issues could inherit their due_date from their fixed_versionClosed2008-03-03

Actions
Actions

Also available in: Atom PDF