Fields are still editable on the Change request created from Standard Change Template, even after including those in "readonly_fields" of the Standard Change properties.Issue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Fields are still editable on the Change Request created from Standard Change Template, even after including those in "readonly_fields" of the Standard Change properties. Release Any supported release Cause Client script "Mark standard change fields readonly" has been modified. Resolution We have a Client Script in the OOTB named "Mark standard change fields readonly" which make the fields Read-only on the Change Request created from Standard Change Template.This is an onLoad client script defined on the "change_request" table.The client script checks for the values entered into the "Read-only fields" field in the Standard Change Properties page.Change>Administration>Standard Change PropertiesIf this client script has been modified or the script which verifies the system property has been altered, the fields won't be set to read-only.