+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 version#36 first, we have several more available filters for date issue attributes.
Below is a complete list:

|_\5. Issue-filters available for issue attributes of date type & issue custom fields of date type |
|_. Date attribute |_. Filter |_\2. Formfield(s) |_.Exceptions/notes |
|=. _foo_ | @is@ |\2. datefield | |
|=. '' | @>=@ |\2. datefield | |
|=. '' | @<=@ |\2. datefield | |
|=. '' | @between@ | datefield (from) | datefield (to) | |
|=. '' | @in less than@ |\2. integerfield (days) | Except for created and updated issue attributes |
|=. '' | @in more than@ |\2. integerfield (days) | Except for created and updated issue attributes |
|=. '' | @in@ |\2. integerfield (days) | Except for created and updated issue attributes |
|=. '' | @today@ |\2. - none - | |
|=. '' | @this week@ |\2. - none - | |
|=. '' | @less than days ago@ |\2. integerfield (days) | |
|=. '' | @more than days ago@ |\2. integerfield (days) | |
|=. '' | @days ago@ |\2. integerfield (days) | |
|=. '' | @none@ |\2. - none - | |
|=. '' | @all@ |\2. - 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 version#36 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.


--------------------------------------------------------------------------------

relates,New,11001,Better date field