Hello,
I would like to request this enhancement:
Background:
There are many circumstances where you will want to have a validation rule to ensure some actions are performed prior to closing a top level project. To do this, it is natural to use a validation rule on the top-level project or program. You may need to complete some financial action, send a customer satisfaction survey, etc. And in this validation rule, it makes sense to monitor the State of the top-level parent. If the state changes to Closed, ensure that the required actions are completed.
Problem:
If you have a project with sub-projects, tasks, etc. and the last task on those plans is closed, that change "rolls up" to the parent project.
Clarizen business rules cannot seem to 'detect' a change in status on an object when that state change was caused by a child task being closed. For example, if the validation rule initiates when IsChanged($State) for the parent project, it will never execute even though the state *does* change due to the last child task closing.
REQUEST:
Please make it so these state changes are detectable as a state change, so we can run these validation rules on the parent project.
Please sign in to leave a comment.
This is a major issue for me as well. Projects are constantly being marked as Completed automatically when they shouldn't be.
I've tried various validation rules, but as the author above states it doesn't pick up State changes which have been triggered automatically.