Feature request: Gantt chart task with multiple dependencies

[wigy-opensource-developer]

There are cases in a project when multiple tasks has to be ready (apple and banana) in order to start with a given task (cherry).

gantt
  apple :a, 2017-07-20, 1w
  banana :crit, b, 2017-07-23, 1d
  cherry :active, c, after b, after a, 1d

Loading

It would be intuitive if I could just express these dependencies by adding multiple after properties to the task.

Is there a way I can workaround this missing feature at the moment? If either start time or duration changes on apple and banana, I need to remember to update cherry to depend on the one with the latest end time.

[DougHughes]

totally, drawing a line from the end of task to the beginning of a dependent task when the start of the dependent task doesn't line up (because it has other dependencies) would also be useful. This is particularly important when the dependent task is in a different section (different parallel project). Having a line from the end of the task in Proj1 to the beginning of the task in Proj2 when there's a gap, would be illustrative. (dotted, whatever)

[CraigDamlo]

This may be a second feature request, but to build on the apple, banana, cherry example, sometimes I need a delay, like start apple 1 week after banana; both beginning and ending.

[fbartho]

I too also want this feature!

Additionally, sometimes it might be convenient to have a before taskId statement.

[fbartho]

I think this is the interesting code for this feature: https://github.com/knsv/mermaid/blob/a4992963b3873ec7a566ba91b92596d2a360e3b9/src/diagrams/gantt/ganttDb.js#L66-L76

Are there any more things to look at?

[peetervois]

I also need this feature. And I also found the code by fbartho. It seems to me that a loop would be needed to look through every afterStatement[x] and return the task.endTime that is the latest. Would it work?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you are still interested in it, and it is still relevant, you can comment or remove the label to revive it.

[wigy-opensource-developer]

ping for you, @github-actions

[stale]

This issue has been been automatically closed due to a lack of activity. This is done to maintain a clean list of issues that the community is interested in developing.

[peetervois]

Thank you for keeping it open. I am watching this issue. I am ready to set up premium for those who decides to solve it and make new release for https://www.dokuwiki.org/plugin:flowcharts .

[peetervois]

The change is going to be published soon. Stay tuned.

[IOrlandoni]

@itprdev If you'd like, leave a comment here so I can assign the issue to you so nobody else works on it and when we close it you'll permanently show up as the user that fixed it!