Hi Dan,
My understanding of Marcus' request is:
- to insert the new task at the same level (tree / hierarchy)
- (as
a consequence) to shift the dependency references to have the new
inserted task "incorporated" in an existing dependency sequence flow.
However, if I decode your reply correctly, you propose to insert it as a subtask of an existing task having a dependency sequence flow - not the same usage IMHO.
I
have already been many times in situations where I had to make manually
this job of dependent task insertion + dependency references shifting.
I understand very well the benefit of this feature and would really appreciate to have it available.
Of course, it would save time. But mainly it would ensure the dependency references shifting is correct.
I must admit I already messed some dependency sequence flows during my manual adjustment exercises.
However... this new concept of inserting a task could collide with the existing concept of adding a task. [1]
Considering the trigger of the intention:
- if it is the task position in dependency sequence flow >> you could insert 'before' or 'after' = 2 cases
- if it is the task position in tree / hierarchy >> you can add 'below' (or maybe soon 'above' ) = 2 cases
It
makes a total of 4 cases (= before below / before above / after below /
after above) to foresee in the menu >> quite complex IMHO
And so far, I can't see an easy solution to take the best of both worlds, other than just add it in the menu situation 'as is' - still thinking...
Have a nice day - Eric