Configuration Manager for Jira - TTS Integration

After the 10.7.0 version is released, TTS now has been integrated with CMJ. It is possible to export and import TTS configurations by using CMJ. The followings explain, according to the snapshot type you select, it can be seen how the configurations are moved.

Open

Snapshot Type:

Open

• SLA Configurations that do not have any project selected will be moved.

• SLA Panel data will be transferred. If Card Context contains SLAs, they will be flat-mapped. This means new SLA will be added into the list whereas the old one stays.

• Settings - General Tab, JQL will be mapped. Be careful with any references used in JQL.

• Settings - SLA Notifier Tabs data will be moved.

• Settings - SLA Calculation Scope: Projects and Issue Types will be mapped.

• Settings - Scheduled Task: Data will be transferred.

• Settings - Advanced Tab: Data will be transferred.

• Permission: Groups and Project roles will be mapped.

• Since Calendars do not have any reference outgoing, all calendars will be cloned into the target instance.

• If an Escalation Service does not have any SLA reference then this means it applies to all SLAs, therefore this escalation service will be exported. Escalation service's name will be changed when importing. In case there is an escalation service with the same name.

• If a Report Configuration is meant to be applied for all SLAs then this report will be exported. 

• Only the SLA Configurations related to the projects will be exported. Along with the SLA configurations, SLA notifiers will be moved.

• SLA Goals may refer to calendar configurations. Only these calendar configurations which are related with the SLA goals will be exported.

• Escalation Services may refer to SLA configurations. If an escalation service refers to SLA configurations that are not being exported. These SLA references will be deleted. And if an escalation service has reference no for the SLA configurations that being exported, this escalation service won’t be exported. Escalation service's name will be change when importing. In case there is an escalation service with the same name.

• if a Report Configuration does not have any references for the SLAs being exported. Then it will be dismissed.

• Issue SLAs are main issue-related data. We let the users re-generate SLAs for issues in order to produce more precise data and avoid any degeneration.

• Gadgets may refer to projects and SLAs. Consider that if an SLA is not found in the snapshot, then it will be deleted.

• Reset post function refers to SLAs. If these SLAs are moved within the snapshot, then they will be mapped otherwise they will be removed. 

• TTS fields may refer to link types and SLAs. These link types will be mapped. If a TTS field has a reference for SLA. Then this SLA will be moved with the custom field itself.