Feature #7575
open
Enhance issue due date fields to also accept an offset
Added by Daniel Reiche about 13 years ago.
Updated almost 7 years ago.
Description
Sometimes the exact due date does not matter when defining issues. Rather more important can be that an issue is due xy days/weeks/months after its start.
It would be cool, if the input fields would accept a kind of offset format (probably +xD, +yW, +zM, where D = Days, W = Weeks ...). Or the datepicker could be accompanied by a multiselect+text field: in xy Days/Weeks/Months.
+1
Very handy feature when creating project plans. Especially, modifying the due date of a preceding task should "shift" the following tasks accordingly.
Those issues seem to be related: #6580, #3195
The whole idea requires of course: #7142 and #2161.
On current source:/trunk (>= r7841), which will evolve into Redmine 1.3.0 first, we have several more available filters for date issue attributes.
Below is a complete list:
| Issue-filters available for issue attributes of date type & issue custom fields of date type |
| Date attribute |
Filter |
Formfield(s) |
Exceptions/notes |
| foo |
is |
datefield |
|
| '' |
>= |
datefield |
|
| '' |
<= |
datefield |
|
| '' |
between |
datefield (from) |
datefield (to) |
|
| '' |
in less than |
integerfield (days) |
Except for created and updated issue attributes |
| '' |
in more than |
integerfield (days) |
Except for created and updated issue attributes |
| '' |
in |
integerfield (days) |
Except for created and updated issue attributes |
| '' |
today |
- none - |
|
| '' |
this week |
- none - |
|
| '' |
less than days ago |
integerfield (days) |
|
| '' |
more than days ago |
integerfield (days) |
|
| '' |
days ago |
integerfield (days) |
|
| '' |
none |
- none - |
|
| '' |
all |
- none - |
|
Knowing this, I'm curious to know whether or not the currently available filters suffice the request in this issue?
Mischa The Evil wrote:
On current source:/trunk (>= r7841), which will evolve into Redmine 1.3.0 first, we have several more available filters for date issue attributes.
Knowing this, I'm curious to know whether or not the currently available filters suffice the request in this issue?
This is cool, but how do I define, that issue #b is due exactly 3 months after its parent #a has started? Or that it is due 4 weeks from when all dependencies have been marked done?
I was looking for a way to define the issue with an offset (and possibly min/max values too - minimal 2 weeks after xyz and maximal of 6 weeks after start), not show issues due in xy days/weeks/months which is what this filtering will do.
Though, this filter will help in reviewing issues and checking for urgencies or delays.
+1
This feature is pretty common to project management software and required in many project-management methodologies.
And the way it should work is following:
When new issue is added, relation field is also given (follows, precedes) next to parent issue field, currently it is available after issue is created.
So, changes:
- relation field to be added on new issue screen instead of after issue creation.
- next to delay field, duration field should be given, and it will automatically set due date (delay sets start date, and end date is set by delay + duration).
- once preceeding issue is closed, if it's closed earlier then it's end date, issues which are in following relation should be automatically re-calculated.
- Related to Feature #25701: Dynamical dates in import issues functionnality added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by