V2.2.3
When you closed an project but not activity; Project is hidden in "Planning" but not in "Real Work allocation" is it normal, please ?
Yes and no.
In fact, it is not normal to close a project with not closed activities...
But the behaviour is as expected :
- Planning does not display the project, because it is closed...
- Real Work displays : activities are displayed because reource must be albe to enter work (or set left work to zero) on non closed activiites.
Is it possible to modify that, or not , please ? 😛
Ticket #703 created : "Do not close project with not closed items (activities, tickets, ...)"
To be studied : either it is a great constraint, or all depending items must be automatically closed.
Can we also modify the behaviour of sub-projects. In many cases sub-projects used as a hierarchy for easier view rather than real subprojects. Is it possible to keep this hierarchy but optionally not take in account real dependence?
Is it possible to keep this hierarchy but optionally not take in account real dependence?
Sorry, I don't understant the request.
If you just need a hierarchic level, why not just use a parent activity instead of a project ?
Because it too big. It is a project with multiple activities but common components, so hierarchy we are using is like:
version 3.x
- 3.1
- 3.2
- 3.3
But you can define an actitivty as a parent activity
Version 3.x => Project
- 3.1 => activity
- activity 1
- activity 2
- 3.2 => activity
- activity 3
- activity 4
- 3.3 => activity
- activity 5
- activity 6
It will be huge and unmanagable list unfortunately.
Actually the only problem we have with current structure is the project closure
But what would be best : autoclose or control ?
- auto close all items (tickets, activities, ...) on Project closure
- control that all items (tickets, activities, ...) are already closed on Project closure
I would prefer to have an option but generally control is better
Hello,
quote:
To be studied : either it is a great constraint, or all depending items must be automatically closed.
Have you developed a functionality to close a project with unclosed depending items? You were right back then in 2012... It is a great contrain and pain in the a$$ to close like 100 sub-activities manually before being able to close the main project. Yhere should be some on-click solution...
Best Regards,
Robert
As it was requested, it is a control that has been implemented.
Auto-closure is not planned.
But it's easy to close many items with multiple update feature.