-
-
Notifications
You must be signed in to change notification settings - Fork 7.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gantt Chart - <time> after <taskId> - for setting delayed start #818
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I understand what you are after. This is a good idea! Not in place though but I will add it to the project backlog. I am hoping for a larger team moving forward to be able to implement things like this. #866 |
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. |
I would also like to see this feature. Commenting to revive as a potential TODO. |
agreed I like this feature |
The addition of this feature would be great. This would be very useful for the definition of deliverables, which usually have a due date after the completion of the task. |
Yes I agree, this would be nice. |
Chiming in on this too - it's more or less necessary for projects beyond the most basic. |
+1 as a feature request. |
+1 this is a primary roadblock preventing me from using mermaid to capture things beyond simple scenarios. I would love to see something like the following allowing tasks to fill gaps between milestones/tasks as well as a date offset relative another date.
Edit: corrected spelling/syntax |
Would you rather go for:
or
offset being something like Shall the offset be linked to one specific task ? parsing issue may occur if |
@eikelben for the fill the gap feature you can use
gantt
dateFormat YYYY-MM-DD
axisFormat %m-%d
weekday Monday
SECTION Fill Gap
Item one :milestone, itemOne, 2025-02-06, 0d
Item two :milestone, itemTwo, 2025-02-16, 0d
Item three :active, itemThree, after itemOne, until itemTwo
|
@mutricyl It would appear that the issue I was encountering with gantt
dateFormat YYYY-MM-DD
axisFormat %m-%d
weekday Monday
excludes weekends 2024-12-24,2024-12-25,2024-12-31,2025-01-01, 2025-01-20, 2025-02-17, 2025-04-18, 2025-05-26, 2025-07-04, 2025-09-01, 2025-10-13, 2025-11-27, 2025-11-28, 2025-12-25
SECTION Fill Gap
Item one :milestone, itemOne, 2025-02-06, 0d
Item two :milestone, itemTwo, 2025-02-16, 0d
Item three :active, itemThree, after itemOne, until itemTwo
|
@mutricyl
as this mimics the standard syntax.
I'm not entirely clear on this. If I am understanding you correctly, yes the task offset should only apple to the current item. In general the scenarios I encounter are where an item should occur a set duration before or after a milestone occurs – "a week after permits are approved, then x" or "5 days prior to drawings being submitted for approval, x needs to occur." Does that help? |
It looks like a feature. You defined a milestone at an excluded date which is a little bit odd. Then for Edit: deeper look on the interaction of |
I have worked a little bit on this feature, and I have a workable example. I do not want to make it too complicated so I went with a I have to finish the tests and update the documentation before submitting a PR. To be more precise on the parsing issue mentioned above: |
@mutricyl Sorry, my example was hastily pasted without noticing that. As you discovered, the same error is present even when that date falls outside of the excluded dates. Thanks for investigating. gantt
dateFormat YYYY-MM-DD
axisFormat %m-%d
weekday Monday
excludes weekends 2024-12-24,2024-12-25,2024-12-31,2025-01-01, 2025-01-20, 2025-02-17, 2025-04-18, 2025-05-26, 2025-07-04, 2025-09-01, 2025-10-13, 2025-11-27, 2025-11-28, 2025-12-25
SECTION Fill Gap
Item one :milestone, itemOne, 2025-02-06, 0d
Item two :milestone, itemTwo, 2025-02-19, 0d
Item three :active, itemThree, after itemOne, until itemTwo
|
Just to make sure I'm clear, does that mean an offset can only apply to the start date of the task? Are offsets on either/both the start and end date possible, as in my initial example?
The specific use case I have in mind is to create a generalized project schedule where all task dates adjust automatically based on a single initial start date. This requires defining task relationships using date offsets and durations rather than fixed dates. You might ask, “Why not just use a Gantt chart application?” My answer is that this approach produces a more static, presentation-friendly visual—ideal for sharing a high-level view without the complexity of interactive tools. The goal isn’t to map out an entire detailed roadmap, but rather to provide a representative illustration that is reasonably accurate when produced. Once the project kicks off, individual tasks would be managed through other tools or processes.
That seems to add an unnecessary level of complexity which is both unfortunate and surprising. Thanks for the time and effort spent on this! |
I do indeed intend to be able to use either |
As described in the following comment (#552 (comment)):
Consider the following Gantt chart:
I'd expect to be able to be able to perform the second task 1 day after first task concludes via
1d after first
. Perhaps there is already a way to perform an offset/delay buffer that hasn't been documented?I've unsuccessfully attempted to create a hidden buffer task to use as the start date, which did not work because I could not control the styling (it was still visible); below should help exemplify my effort:
Please let me know if this needs further clarification and feel free to use the demo for a working reference.
The text was updated successfully, but these errors were encountered: