When raising a standard change via a standard change template, some field values are deleted/cleared.Issue When creating a standard change using a template, the values in number, opened at, opened by, state, conflict status and type fields are cleared.ReleaseAllCauseThe issue is being caused because the affected fields were added to the Read-only fields section of the Standard Change properties. Steps to reproduce: Create a Standard Change template.Navigate to Standard Change PropertiesIn the property "List of fields that cannot be altered on a Change Request created from a Standard Change Template" add one/some of the fields that are auto populated when the change form is loaded. eg Number, State, opened_at, etcSaveOpen a new standard change. ie. Change > Create new > Standard ChangeNotice the new form loads and some of the fields are pre-populated . eg Number, Type, StateCreate a Standard change using the test template that you created.Notice that the fields that are auto populated when the change forms loads are now blank if they were added to the property referred to above.ResolutionThe issue doesn't occur when the OOB business rule "Restrict fields from Standard Change" is disabled. In this scenario, reproducing the issue with debugging tools showed the following: 14:58:26.766 Time: 0:00:00.000 for: xxxxxxxxx[glide.17] SELECT ... FROM std_change_properties std_change_properties0 WHERE std_change_properties0.`internal_name` = 'main_config' /*...*/ //field values that are cleared:14:58:26.770 Global conflict_status: Not Run =>14:58:26.770 Global opened_at: 2020-07-01 12:58:14 =>14:58:26.770 Global opened_by: user.name.@snc =>14:58:26.770 Global state: -5 =>14:58:26.770 Global type: standard => The business rule - Restrict fields from Standard Change https://instance_name.service-now.com/nav_to.do?uri=sys_script.do?sys_id=ddfb8160938102009ca87a75e57ffbb4Has this line of code which references the StdChangeUtils script include change properties . if (current.operation() === "insert")new StdChangeUtils().reapplyReadonlyTemplateFields(current); Commented out this line of code and the issue doesn't occur. The business rule and the script include it calls StdChangeUtils were OOB. Checked the change properties and the property "List of fields that cannot be altered on a Change Request created from a Standard Change Template" had the option to add fields to the Read-only fields section. And all the affected fields in this scenario are present in this section. Removed one of the fields and reproduced with the OOB business rule, the field is no longer cleared, this is the cause. Solution is to remove the fields that are being cleared from the Read-only field section in the Standard change Properties here:https://instance_name.service-now.com/nav_to.do?uri=std_change_properties.do?sys_id=527b5dafff700200b18affffffffff89