[SOLVED] Real work allocation - Bad allocation after input

Hi Babynus,

Something strange that happends for the first time since I use ProjeQtOr (since 2011, october).
In Real work allocation screen, when I write 0.25 and save it, that is correct. The sum of the day is 1.



But after refreshing the screen, the value is changed to 0.5 and the sum of the day is 1.25, which is wrong.



How is it possible ?
I try to correct this value, but even after saving, submitting, validating work, it's always change to 0.5.
I don't understand...

Do you have an idea ?
Thanks
Fred

Hi,
I'm on V 5.4.4

If that can help, here is the main screen of this activity :

Hi,
I think my way to use ProjeQtOr is not quite correct.
- I use only 1 project : the "master" project. And then, I use activities.
- Since 2 weeks, I use sub-activities to be more precise. But it works bad with real work allocation screen : sub-activities does not report the total in their "master-activities" allocation line.

So I will change my way :
- rather than activities, I will use sub-projects.
- then sub-activites become activities. I think it will be more correct.
And perhaps, the real work allocation screen will work more properly than today.

Hi,

At first, for this 05/08/2016, I have 3 allocations (on 3 activities).	- Soutien => 0,25 - Recette => 0.25 - Etudes => 0.5 The sum is = 1 (day)	But after leaving and return to this activity screen (#31)	soutien = 0.5 and so sum = 1,25 (my first post).
I have try to write another time	soutien = 0.25	but the problem persists.	soutien = 0.5 sum = 1,25 (my first post).
Today, I try this :	- Etude => 0.25 - Soutien => 0.5 (no change) - Sum = 1	After coming back to the screen :	- Etude => 0.25 - Soutien => 0.75 !!! - Sum = 1.25
Another test	- Soutien => 0 - Sum = 0.75	After coming back to the screen :	- Soutien => 0 - Sum = 0.75
Last input :	- Soutien => 0.25 - Sum = 1	After coming back to the screen :	- Soutien => 0.25 - Sum = 1

That is finally correct !!!
And now, the real work allocation screen remains correct !
It seems like I had to write and save a zero value (0) for Soutien allocation, before write the correct value...
It's the first time this problem occurs...

If this can help...
Fred