Hello,
when i use "close" for an activity to make it to disapear from real work table, parent activity is reduce as if closed activity not exist (even if i use "show closed items").
I attach a screen copy to help you undesstand my poor english 🙁 !
.
Sorry, I don't understand,
and screen copy is not attached 🙁
Here are few questions to try and understand :
- What do you mean by "close" the activity : set it to a closed status ? With closed status checkbox checked ?
- What do you mean by : parent is reduced ?
- IS the resource assigned to both activities, parent and closed one ?
My test is :
Activity 1
Activity 1.1
Resource R is assigned to Activity 1.1.
=> On real work for R, I see 1 and 1.1.
Then I close 1.1.
=> On real work for R, I do not see 1 and 1.1 anymore.
Then I assign R to 1
=> On real work for R, I see 1.
=> only strange behavior, is that I have a cross to expand Activity 1, and when I click on it, it expands to ... nothing. This ios due to the fact that 1.1 exists, even if not displayed.
If I select "show closed"
=> I see 1 and 1.1
All seems correct to me.
Please describe complete test and what you expect.
Sorry, i attempt a new attachment...
Close activity : closed checked with date
Parent reduced : I meen that, in Gantt, you will see parent activity size decrease according to status of dependant activity, even if you ask for viewing closed ones.
Ressource is or not assigned to parent
Regards,
Hi,
If and can reformulate the description.
You have 1 parent activity (1) with 2 (at least) sub-activities (1.1 and 1.2).
When you plan, parent longs from start of 1.1 to end of 1.2.
If you close activity 1.1, then parent activity 1 longs from start of 1.2 to end of 1.2, as if 1.1 do not exist any more.
This occurs even if you display 1.1 (using show closed activity) : this way, you see 1.1 starting before start of parent 1.
Is that correct ?
On which version of ProjeQtOr did you face this issue ?
For information, I tried it on V4.2.1, and all was correct (on following print screen, activity 6.2.1.1 is closed)
Youre correct, this is exactly the problem.
We are in V 4.1.2 actually.
OK, I'll try and repproduce.
It should be linked to specific situation.
Ticket #1331 recorded.
For information, I could reproduce only when artivities are closed "with no real work entered".
This is fixed, and will be deployed in V4.2.2.
Fixing will need planning recalculate to display correct values.