Business rule affecting project Tasks

[Derek10]

I'm looking for the business rule that affects the following:

New project tasks in the SN Project module are set by default to be in an Open state. If the project itself is in a different state, creating the new task will set the overall project state to Open. Likewise, changing a project state can change all the related project tasks to the same state as the overall project.

It seems we had a issue where the project was moved forward a phase, then moved backward and it reset all of the existing closed tasks.

Has anyone run into this issue?

[solonxu]

Thanks Kelly. I misunderstood.... our issue is, the project (pm_project) table have multiple custom states, which are always rolled to Project Tasks when state changes (BR: Process State Change). I am wondering if there is a way to skip/bypass the business rule, for example, a project have 'Pending' and 'Awaiting Info', when the state changes to Awaiting Info, project task state should not change. Any idea? Thank you very much.  

[kellykaufmann · Accepted solution]

Hi Solon - one big lesson we learned this past year is to not mess with the built-in project states or project task states. There are tentacles EVERYWHERE that you will days, weeks, months later realize you broke some functionality by not using   or changing certain states. In the end, we ended up undoing all our changes and going back to OOTB, and speaking with SN about some changes coming in Geneva that would solve some of the challenges we were having that was leading to us making all those changes. I suggest instead you reach out to SN regarding their planned Geneva changes to see if that will fix what you need as well.

[solonxu]

Thank Kelly. I agree. That is what I found for the OOB scripts. We don't want to break any existing rules. I appreciate your comments.