+1 please

So what became of that SLA work that was happening 2 years ago? Why wasn't this selected? Ben? 

While this feature is unavailable in Jira, you can change the SLA name, make a copy, reset and do other things using the SLA Time and Report for Jira add-on.

By the way, there is also a free plan for a team of up to 10 users. You can try all the app's benefits with a 30-day trial version.

How do we at least get a response on these tickets?  You have SLAs for Jira Service Management, but they are not relevant to any operations teams outside of basic ITSM functions.

I understand this doesn't make you any additional revenue, but this is basic functionality.

Hi Team, would like to see the option to change the sla name in Jira other than the one's shown by default. Please consider this.

Hard stuff not to rename a SLA while concepting and trying to set-up JSM for my organization. This option should be available. Please

Please add this as an option 

Oh my god. PLEASE, allow us to rename a SLA. Jesus.

Currently, if I decide to give an SLA another name it seems like I have to delete and re-create. Not ideal, to say the least.

Voted for this feature request, please consider! This feature request is still relevant.

At a bare minimum, please provide an option to copy existing SLAs and allow them to be renamed at that point. Still not as ideal as simply being able to rename an existing SLA, but better than having to manually recreate an SLA each time you just want to change the name.

+1 please 

This is yet another example of different parts in Jira behaving differently. One can rename a workflow, a custom field, and many other entities, so why not an SLA?

Since every entity in Jira is uniquely identified by an ID (and I assume an SLA is too), this should be easy-peasy.

IMO, all product managers for Jira should be put in one room and not allowed to leave until they take a vow to have these two features implemented in their respective entities:

1. Ability to rename the entity (example for one that does not: SLA)
2. When editing an entity, there will be a 'Save' button and a 'Cancel' button (example for one that does not: 'Configure screen')

NEED

Both when you create a new SLA as well as when you edit an existing SLA. 

Would go well with the ability to Copy an SLA.

We need it! 

need  

Ability to rename would be very helpful. Or at least a roll-over so that the full SLA name can be seen in the issue view.

How can we bump up this priority?  This seems like such a trivial feature to allow a custom label on top of a DB field.  What is the point of allowing custom workflows for tasks/tickets and not allowing the user to customize their SLA within the process?  Happy to discuss further.

+1 - Please allow us to rename!

Open a case with support and have them unlock the field so you can go delete. It worked for me but you didn't read that here though.  

Exactly... how the heck do you remove an old SLA that's no longer used?  Hack/slash the backend database?

It's because of the limitations that ORM layers impose on application design and the way that Jira has been developed around the ORM layer that makes these sorts of things difficult 

This is a very simplistic explanation but should convey the gist.

Traditional database applications would just reference an ID of something. SLA ID would typically be a numeric id like 123, and the name of the SLA wouldn't matter.  Issues would just reference SLA 123 and be done with it.

But Jira doesn't use ANY standard database nice-ities like foreign keys or triggers or anything like that... they do that all inside the application (to maintain database neutrality, but with a side-effect of limiting capabilities of the application and makes development more difficult).  But that doesn't mean you can't do renames... if they had the forethought to design it with renames in mind, there are other ways.

Without things like foreign keys, it makes life difficult because you lose the automatic handling of things like changing the name of something.  There's other design problems like the fact that Jira references things by NAME instead of internally by ID. Filters are another culprit.  When changing a filter name, expect MANY things to break!

So something 'simple' like renaming an SLA might take dozens or more of man hours to fix because they have to re-write all the internal layers due to design deficiencies in the original work.

The workaround listed doesn't work for Cloud, as we don't have direct access to the database. I don't get why this is such a huge deal.

+1

+1

+1 There are many reasons to need to change the name of an SLA. This should be core supported functionality.

It's pretty weird that SLA names can't be changed when pretty much everything else is editable.

Oh well, one more vote.

This feature would deliver value by giving the IT support business more flexibility

I think it's something we shouldn't even have to ask for, but alright.

We need this feature as well

I understand that there is a workaround but I think that this should be available in application layer;
Will this task be implemented in JSD in short time?

I agree with others, this feature is fairly important

Still no updates... For such a key request?

Another factor I just came across... new SLAs don't get calculated for closed issues. So if you need to create a new SLA as the only option for renaming one, we will lose all our SLA data for any closed requests.

This is a big inconvenience. Creating a new SLA is not so bad, but I've got loads of dashboards that display SLA metrics so I'd have to review them all and update the filters that are looking for the old SLA and switch them to the new SLA.

atlassian679,

In case you haven't figured out how to delete an SLA, you can:

• go to SLA page
• hover the mouse onto the SLA you'd like to delete (in the left panel)
• click on the arrow that shows up and Delete

I've updated this ticket with a workaround for renaming SLAs. Please check it out.

I'm interested in this feature too.
Until then, can somebody tell me how I can delete an SLA?

Yes, we need it!

Hello,
It is really time consuming to delete an SLA and create a new one just in order to change its name especially if you have a lot of service desks. It is important to have this possibility.

Oh please...