The job templates must reuse some fields of the previous instance

Update:

• title changed from "The job templates should not force disable=false"
• resolved NXBT-2725 as duplicate
• when producing an already instantiated job, the template should look at some of the existing fields in order to preserve them
  • disabled
  • description
  • other fields (to be determined) which are customizable from the UI despite the template relationship prevent the use of /configure for anything else than the template parameters

—

See NXBT-2722, it's confusing that a disabled job gets enabled back because of its template.

Do not set disabled=false in job templates.