Migrating changes to templates

 

How does this migration work?

With the release of the change template feature, all current change requests in the application will be automatically assigned with the default template (general template), along with the additional fields.

Any new additional fields that you create will be listed in the right pane of the default template. You can map them to the template by editing the template.

 

Migrating change statuses

With the upgrade of change status to change stage status, the existing statuses must be migrated under specific stages.


Who can initiate the migration process?

SDAdmins. 

Other technicians need to consult with the SDAdmin.

 

How to migrate the statuses?

The displayed page provides the default mapping of the old change statuses with the new statuses and stages as follows:
 

Old Status

New Status/Stage

Rejected

Rejected/Submission

Completed

Completed/Close

Other statuses (For example, Requested)

Requested/Submission

No status assigned

Requested/Submission

 

 

Once the migration process is complete, you cannot undo it.

 

Is the manual status migration urgent?

No. You can choose to migrate at a later point. However, the default migration will happen with effect from the release of the latest build.