What’s new? v4.60 – Profiles or roles for planning

v4.60.0 — Planning with profiles, before you have names

v4.60.0 — Planning with profiles, before you have names

• A task can now call for a profile instead of a person. When a project kicks off, you know you need “two functional consultants,” but not yet who. Now that can be captured as is: the task form has a “Required profile” field, next to the owner field. There’s no longer any need to make up a generic user that later clutters the directory and the reports.
• Profiles carry a rate. In Settings, each project role can have its hourly cost and billing rate. With that, the project’s planned cost is real from day one, when the team is still a list of profiles. In the budget panel those rows are flagged as pending to be filled.
• Workload balancing shows what’s missing. Tasks that call for a profile and have no person appear at the bottom, in “To be filled” rows, with the committed hours per week. They aren’t added to anyone: a role’s capacity isn’t a person’s, and loading them onto someone would show an overload that doesn’t exist. That row is exactly the signal of whom you need to hire or free up.
• Once you know who, everything is filled at once. When you assign a person to a profile, all the tasks for that profile in the project are put under their name in a single step, and it can be undone if it was a mistake.
• The profile doesn’t disappear when someone is assigned. It still states which profile the task requires, which is plan information and is useful for the next similar project. Includes a migration that runs automatically when you update. Update backend and frontend together.

← Back to the index