Actual start and Actual End Dates are not updating after change Task closed

[Gopal14]

Hello,

Actual start and Actual End Dates are not updating after change Task closed.

This is working fine for Normal, Standard, Emergency.  

Now we have created a new change type as well, for that this functionality is not working.

I found below business rules.

/sys_script.do?sys_id=0b0217e25323101034d1ddeeff7b1206&sysparm_view=&sysparm_record_target=sys_script&sysparm_record_row=4&sysparm_record_list=scriptCONTAINSwork_end%5EORDERBYname&sysparm_record_rows=7

sys_script.do?sys_id=01c05fa25323101034d1ddeeff7b125a&sysparm_view=&sysparm_record_target=sys_script&sysparm_record_row=2&sysparm_record_list=scriptCONTAINSwork_start%5EORDERBYname&sysparm_record_rows=6

If I change here does it will work for my new change as well

[Aditya_hublikar]

Hello @Gopal14 ,

 I think this might work . you can try that in your pdi .But i suggest  you instead of modifying OOB rules directly, 

create your new business rule same exact as both of them and then test your custom model on that . This will help you test your custom model without affecting OOTB behavior. 

If this helps you then mark it as helpful and accept as solution.

Regards,

Aditya

[Dr Atul G- LNG]

Hi @Gopal14 

I think you are creating technical debt for your instance. Creating a new change type is not recommended. It’s not just about adding a new type—you also have to rework the flows, build logic for visibility, and handle other related configurations.

It’s better to use the existing change model. This way, you can avoid creating technical debt, which is the best approach.

https://youtu.be/UV_Tac-AVDw