There does not exist a user friendly way to export and import SLA’s from one environment to the next. A ticket was opened with Eptura (416847) to inquire about this and it was recommended to go the manual route via certain tables, though this list did not contain tables that interact between SLA’s and the Corrective Maintenance console. We, and others across the enterprise would like to see an easier way to transfer SLA’s between environments.

Latest from the ticket referenced above is: "There are not any pre-built processes for transferring SLAs between environments; you would need to export the component tables from the source environment and import them into the target environment one-by-one."

We have several different environments; Staging (DEV), Training, and Production. We develop in Staging, use Training to build data and processes to test, and migrate things to Production. We also often refresh the other environments with current live data so that we can perform accurate trainings, demos, and build in a "live-ish" environment before Production. This refresh effort, which we overwrite the entire DB/files, causes Users to have to go into the environment and extract all of the pertinent data that they are working on, and re-import when after the refresh.

The intricacies of the SLA's, open tickets in the Maintenance Console, SLA's Ordering Sequences, all of the different tables that are involved in the creation and usage of the SLA's, can be very time consuming to replicate manually across environments.

The ask is for a Admin/User friendly way to select SLA's, copy them, and transfer them and integrate them into the next environment that also takes into account; open tickets, SLA ordering sequences, etc. Thanks.