Hi.
At the moment I see that is possible to change the Project of an Activity even if it has attributions, requestor, responsible. In this way you can get attributions of non-affected resources, requestor that is not related to the project client and so on.
I think that a check of this consequences in order to reject the update could be very expensive; reset requestor if not valid and adding automatically requested affectations quite dangerous.
What about to make project a read-only field after activity creation ?
Let me know your opinion, please.
Thanks for your attention
What about to make project a read-only field after activity creation ?
I don't think it may be a good idea, because it often happen that you create an activity (of other item) on incorrect project and want to change it afterwards.
I agree this may lead to unconsistency, but this already exists without changing project :
- you can delete allocation to project for responsible or for assigned resource
- allocation to project may end (end date reached) with same result
- you can select a reponsible through magnifier icon and select a resource that is not allocated to project.
As you see, there may be lots of such unconsistency, and I don't think it is ourpose of tool to control this.
Project manager should know what he does...
Ok.
I will try a different approach. I agree that manager should know what he does, but when he realize that an activity has been linked to the wrong project, he will need help to make correction (including real work imputations and billings ). So I see two options : the code is able two correct all inconsistencies or the manager drops the current activity and reenter all data in a new activity linked to the right project.
I'm not worried about affectations/assignment inconsistency; do you think that it can be a problem in follow-up or other activities ?
Thank you for your attention.
So I see two options : the code is able two correct all inconsistencies or the manager drops the current activity and reenter all data in a new activity linked to the right project.
Yes, projeqtor does this !
But as I described previously, this may lead to have real work (and planned work) for resource not allocated to the project.
En poursuivant votre navigation, vous acceptez le dépôt de cookies tiers destinés au bon fonctionnement et à la sécurisation du site (gestion de session, reCaptcha) et à une analyse statistique anonymisée des accès sur notre site (Google Analytics). Si vous vous inscrivez, les informations que vous fournirez ne seront jamais divulguées à un tiers sous quelque forme que ce soit. En savoir plus
Cookies settings
×
Functional Cookies
Ce site utilise des cookies pour assurer son bon fonctionnement et ne peuvent pas être désactivés de nos systèmes. Nous ne les utilisons pas à des fins publicitaires. Si ces cookies sont bloqués, certaines parties du site ne pourront pas fonctionner.
Session
Please login to see yours activities!
Other cookies
Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.
Support us on Capterra
