[REACT] Assigning more than 1 resource in fixed effort task rmeoves data (blocker)

[arnaus]

Hi,

I found a bug with fixed effort scheduling mode, it can be reproduced in bryntum site: https://bryntum.com/products/gantt/examples/resourceutilization/.

const gantt = new Gantt({
    project,
    dependencyIdField : 'sequenceNumber',
    resourceImagePath : '../_shared/images/transparent-users/',
    appendTo          : 'container',
    collapsible       : true,
    header            : false,
    minHeight         : 0,
    viewPreset        : 'weekAndDay',
    tickSize          : 40,
    columnLines       : true,
    startDate         : '2024-01-16',
    columns           : [
        { type : 'name', width : 280 },
        { type : 'schedulingmodecolumn', width : 280 },
        { type : 'duration', width : 150 },
        { type : 'effort', width : 150 },
        { type : 'resourceassignment', showAvatars : true, width : 170 }
    ]
});

Steps to repro:

1. create a new task

• set mode to "Fixed Effort"

• set effort to 40 hours

• set duration to 5 days

• open resource picker and assign 2 resources, one with 90% units and the other one with 60%, save it

Result: duration is set to 0 without reason.

See attached video on how to repro in your demo site mentioned above. Again, this to me is a Blocker bug, it removes user data and has to be set it again, also it can be dangerous when we load the project and computations...

Please set it as top priority, several customers on our side are afected.

Thanks,

[alex.l]

Thank you for the report and clear description! Here is a ticket to track the status: https://github.com/bryntum/support/issues/13191
You can subscribe on ticket updates to be notified when it's done.

[arnaus]

Hi Alex do we know if this one is going to be in one of the next releases?

[alex.l]

Hi arnaus,

No we don't know, but it's high prio and won't take too long to get fixed.