Enable Total Float to work with multiple predecessors.
Currently, Total Float will only calculate correctly when there is a single predecessor for an activity.
Sign in to see the current vote count, add your own vote, or leave a comment.
Yes, I would love to see this capability developed as well. Thank you!
This capability would be very useful for accurately showing which tasks are close to affecting critical path. As currently implemented, I don't see how TotalFloat can be used reliably since only the simplest of projects will not have some tasks with multiple predecessors.
This request was made almost a year ago and the discussion with moderator goes back even further. Does anyone know if its being worked on? Float/Slack is such a helpful/time saving piece of information when managing a schedule.
Another year down…almost. Any word? I had a cobble together my own highly specific code to very poorly approximate Total Float for my work. Our schedules are complex with heavy dependencies…and float is crucial for us.
Hope this gets resolved soon!
Summary of Issue All team members work a standard 7.5‑hour day, but only a portion of that day is allocated for project work (e.g., 25%, 50%, etc.). In Resource Management, however, the system currently interprets allocations as a percentage of the full 7.5 hours, instead of the project‑eligible portion of a person’s day.…
Dashboard widgets are currently mostly static. I can display counts and charts, but I cannot click into a specific part of a widget to drill into the underlying records. It would be a big usability improvement if widgets supported interactive drill-down. For example: Click a bar segment (or stacked segment) to open the…
IDEA: for Workflow automations, add a detailed "modification history" Currently, the Workflow Automation only lists the Created By, Created Date, Last Modified By, Last Modified Date, and Last Ran on. This is missing critical information. It doesn't show any changes to: Automation name Trigger conditions Actions Recipients…
