How to rename SLAs
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Currently there's no way to rename SLAs in Service Management. However, this can be achieved via direct database modification.
This example explains how to rename an SLA from SLA1 to SLA2 in a Service Management with project key SD.
Step-by-step guide
Direct database modification is not supported. Please make sure to back up your database or create an XML backup in Jira before attempting this workaround.
- Stop Jira
Identify the ID of the SLA custom field (notice the use of SLA1 as the name of the SLA custom field):
select ID, cfname from customfield where customfieldtypekey like '%sla%' and cfname = 'SLA1';By default, this custom field is Locked and has the same name as the SLA
Identify the ID of the Service Management (notice the use of SD as the project key of the Service Management):
select ID from ao_54307e_servicedesk where project_id = (select ID from project where pkey = 'SD');As the same SLA can be used in multiple service projects, it's good to make sure that you only change its name where necessary
Identify the SLA itself:
select ID, name from ao_54307e_timemetric where custom_field_id = <ID_from_query_1> and service_desk_id = <ID_from_query_2>;It should have the same name as the SLA custom field, which is SLA1 in this case
To ensure the changes are reflected on (Jira Administration > Issues > Custom Fields) and JQL filters.
update customfield set cfname = 'SLA2' where customfieldtypekey like '%sla%' and cfname = 'SLA1';Once you're sure this is the SLA you'd like to rename, rename it (notice the use of SLA2 as the new name):
update ao_54307e_timemetric set name = 'SLA2' where ID = <ID_from_query_3>;- Start Jira upon executing the queries.
There is a feature request for this functionality to be native to Service Management at: JSD-119 - Getting issue details... STATUS