Bug linking project task to change request

[Community Alums]

When you link a Project Task to a Change Request, the State becomes read only on the Project Task because it is linked to that Change Request. When the Change Request goes into the "Implement" state, the Project Task state changes to "Work In Progress".

The problem: When the Change Request state changes to "Closed", the Project Task is still in the "Work In Progress" and does not moved to "Closed Complete" like it should. And since the State field on the Project Task is read-only, there is no way to close it out, which also keeps the parent Project record open.

[Lukas B]

True, we have the same issue here. My only solution was to force update the state via Script and gr.setWorkflow(false);...

[Simon Christens]

I just tested this and to me it seems to work as intended.

Issues can be caused if logic have been customized.
Heres some general overview of fields synced - a project task does not close unless ALL childs are closed.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0715293 

Also on the task,state field theres a Dictionary override for planned_task that should have the following attributes (Also noted in the knowledge article) because a script will look up these 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,skipped_states=4;7

So in case states have been changed that would also have an impact of handling states towards project tasks