Closed jsonin closed 1 month ago
And into the past... the allocation goes 10+ time-scrolls into the past (I stopped clicking)...
Ok, I found where this comes from.
Step 1) add person to a project [the 3 dots from the All Projects screen]
Step 2) add "hours/week", any number in that field Step 3) go to that project and see that the bug exists, since that "add person" function adds time across their entire lifetime!
If you do not enter data into the "hours/week", the StaffPlan acts normally.
We can fix the bug... but then how do we fix the hours assigned by the bug?
but then how do we fix the hours assigned by the bug?
Were they persisted? I can pretty easily wipe away the time entered in erroneously once the UI bug is fixed.
Anything that has proposed hours past January 2025 and any proposed hours before June 2024....
It should be easy to spot. TY!
Looking strange...