Multiple tasks in same row

Gantt
#1

This question has been already asked many times but there’s no solution so far.

  1. I have multiple tasks that I want to show on the same row.
  2. Each task has many children tasks.
  3. They are not going to be overlapping horizontally.
  4. I’m not using the “task list” feature so it can be disabled.
  5. I want to be able to set row_height etc. differently for some sibling tasks.

What have I tried:

  1. Split tasks feature is too limited for that.
  2. The baseline demo is too limited.

What would be a better solution:

  1. Ability to add another layer of tasks (as in: initializing another gantt on top of current) looks like the only real solution. Can I somehow easily modify the source code and achieve that? I see that I can register a new layer renderer? Is that a solution maybe?

    var layers = gantt.$services.getService("layers");
var markerRenderer = layers.createDataRender({
 name: "marker",
 defaultContainer: function defaultContainer() {
     return gantt.$marker_area;
 }
});
#2

Hello Jim,
The easiest way to display several tasks on the same row is to use the Split Tasks feature. Please, clarify what kind of limitations you encountered and what doesn’t work as you expect.

Another way is to use the Rollup feature:
https://docs.dhtmlx.com/gantt/desktop__milestones.html#rolluptasksandmilestones
If you add the rollup property, the task will be displayed on each parent task with the project type. Right now, there is no built-in way to specify the rollup level or on which parent projects the task should roll-up. The dev team will add that feature in the future, but I cannot give you any ETA.

We don’t provide the guides for modifying the source code or internal functions as they may change in the future, so, you won’t be able to easily migrate the changes.
Instead of that, we recommend implementing the features by using the Gantt API as we inform what is changed after the newer version is released:
https://docs.dhtmlx.com/gantt/migrating.html

You can modify the source code, but in that case, you will need to do it each time you update to a newer version.