Hi Community,
I am a bit unsure whether I should post this here or in the Developer/Architect forum but here it goes:
I've reverted some customisations we applied to pm_project_task and one of them was the State field. Our customisation was that we had choices attached to the table, which where a mix of OOTB ones such as Pending, Open, etc. and some custom ones such as Cancelled and Complete.
We wanted to go back to OOTB behaviour, basically have pm_project_task table use the State choices from Task (as the SN universe intended). We haven't been able to do that because state from Task has some custom choices as well, which we do not want to use in pm_project_task so we ended up turning back on the custom choices we had for pm_project_task and match the values and the labels with the OOTB from Task:
We also created a Dictionary override entry for the attributes:
close_states=3;4;7,default_close_state=3,default_work_state=2,default_open_state=1,default_skipped_state=7,default_pending_state=-5,pending_states=-5,open_states=1,work_in_progress_states=2
The issue we are facing now is that the roll up from Project Task state to Project state does not always work, more specifically, whenever we update all tasks to either Closed Skipped or Closed Incomplete the Project state = Closed Complete.
We know there are some Business Rules that drive this behaviour and these have been left OOTB.
Is there anything else we might have missed - how can this behaviour be corrected?
Thank you.
Paula
