Is this possible and if so how?
If this is not possible would it be possible to have this build into the next update?
I'm using Mindmanager 15
Inserting delay-tasks is certainly an option though that would make the diagrams more complex. I've also thought of splitting the one task into a pre-lag and post-lag so that the dependent task can be linked to the right task. That would also increase the complexity of the diagrams.
Let's say Task 1 is scheduled for 3 weeks and forecast is that after 2 weeks that task provides sufficient information to start Task 2.
In that case I would like to be able to create a Start-Start dependency of Task 2 to Task 1 with a Lag of 2 weeks.
This is just one of the examples to use Lag which is very much used in project management.
However, I could imagine that creating an in-between task called (provide sufficient information to start task2) could solve this. (similar to Nick Duffils suggestion)
And you would have the benefit of keeping track of this in the same way as all the other tasks.
At the time when Mindjet purchased the Cohuman cloud solution, now called Mindjet Tasks, that took those waiting for aspects into account.
We should find out if it still does that after the integration and introduction of the new name.
While the following won't unfortunately provide a workaround, it helps in understanding how this issue arose in the first place.
Prior to version 9 of MindManager it was possible to define a task with a larger number of days between start and finish than the actual task duration. For example, you could give a task a duration of only one day but with the start and finish a week or two apart. While this probably isn't exactly what you describe it may have provided a workaround.
The problem was that until that point Gantt charting for MM maps was provided by a separate program which could be synced with MM - JCV Gantt. This couldn't show this arrangement; anything that was synced between MM and JCV had to have a duration that was equal to the amount of time between start and end date, and vice versa; however, any tasks that had this slack time arrangement in maps that were not synced with the JCV program were unaffected.
When JCV Gantt was integrated into MM itself the rule requiring a duration equal to the difference between start and finish times was also instituted for all MM tasks (much I understand to the chagrin of several add-in developers), so now there is no way of incorporating any slack time into a individual task.