How is this still not available??

+1

This is requested since 2013 and I'm running into the issue in 2022? Incredible...

I can't imagine a world where a user would type something into a box and hit enter and it be incorrect or need to be changed years later.  It's so much more efficient to just delete the offending configuration and re-create it.

Atlassian has shown us the light!

2013... well done Atlassian xd

Really, I'm very interested with this Feature, which I could name: a standard thing.

It is a simple thing to rename something as long as it is not written in stone. There is no big science behind it.

Letting the customer know how data in the DB can be manipulated is a bad approach: https://confluence.atlassian.com/jirakb/how-to-rename-slas-777027027.html

Please put it on your agenda and make sure that the SLA can be renamed.

Wow, yet another opportunity to pay an additional fee for basic functionality that should be included with the base product.  Not only does Atlassian does not care about the voice and needs of their customers but goes out of their way to ignore it. When a third party developer steps in to do Atlassian's job for them, Atlassian can skim off the top when the plugins are purchased from the Marketplace.

Why provide something as part of the product when they can ignore it since 2013 and make more money down the road?

This is shameful. Do not use Atlassian products.

Hi All 👋
We've recently released this feature as a part of the Feature Bundles for Jira Service Desk. This is a new app on the Atlassian Marketplace which bundles useful features for your portal, such us permissions for request types (based on Roles, Groups, Language, Time Zone, and Calendars) or customizable announcement banners. Try 30-day free trial!
In app’s documentation we explain how to rename a SLA name.
Do you need more explanation? Please don't hesitate to contact us via our Customer Portal or book a demo session via Calendly. 🖥
Cheers,

Atlassian doesn't care. They want the community to fix their lack of basic functionality with plugins.

Plugins that can be sold at the Atlassian store so they can skim off the top.

Why fix something for free when you can ignore it for years until someone else resolves it and you can profit?

Customer service, if it ever existed at Atlassian, is dead.

The voice of the customer, if it was ever considered at Atlassian, is scornfully neglected.

Just a side comment on this...you see such inconsistencies across Jira, and here are some that drive me crazy:

1. Most entities can be renamed, but some cannot be (like the SLA we're discussing here)
2. Most editing operations have Save and Cancel, but some do not (e.g. Configure Screen, in which any change that you make cannot be undone).
3. In some drop-down selections, the entities are sorted; in others they are not and God knows what is the order that you see (probably the order they're returned from the database)

I think that Atlassian should convene all the Jira product managers in a room and throw away the key until they fix these problems.

</end of rant>

Amir

This needs to be prioritised. It has been open since 2013

It's disappointing that you cannot rename the field you just created. You have to delete and redo everything.

Well, it been a year since my last checkin on this basic and much-needed functionality. This kind of low hanging fruit is what a responsive software company looks for to provide consistent value to their existing customers. Am I surprised that Atlassian continues to ignore this issue that has been open since 2013?

To be honest, it shouldn't surprise anyone.
One year ago I commented that :

This is yet another example of Atlassian ignoring basic functionality.
This is yet another example of Atlassian ignoring paying customers.
**This is yet another example of Atlassian ignoring common sense.

Atlassian wouldn't be Atlassian if it listened to the voice of the customer over the bottom line on their balance sheet.

A previous admin spelled some of the SLA's wrong within our instance and now the instance is customer facing and it is a bit embarrassing. We don't have the skills on our team to hack the database safely on our production instance. 

We had to go through and create a new SLA with the correct spelling on 40+ projects, (the SLA's were being copied over into new projects). This took roughly 5 hours for one individual to do. 

Please consider this for future releases! Admining a clean up effort at a large scale takes away a lot of productivity time. 

Thanks!

Please fix this Atlassian.  Hacking the database on a production system is not something that is a 5 minute job.  The workaround is high risk and requires a lot of planning (CAB) and regression testing to make sure it doesn't do anything harmful.  I have better things to do with my time.

Would love this for cloud as well

This has been open since 2013.

This is a quick win, no reason not to implement this.

Yet another example of Atlassian ignoring basic functionality.

Yet another example of Atlassian ignoring paying customers.

Yet another example of Atlassian ignoring common sense.

+1 for fixing this – renaming SLAs takes a while (especially since I can't copy one).

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

We would love to see this feature.

We cannot be the only service desk user, who has needed to refine and simplify contract offerings over the years. AND let our customers know about it.

Service desks and more importantly their customer and support arrangements, are not static by definition. But it seems that Jira service desk is not able to facilitate that. This feels a little short sighted for a product that wishes to slot itself into the enterprise market, where changes to service plans such as merges and realignments are commonplace.

As a straightforward use case, just consider how frequently we have each had our mobile phone contract plans adapted without us even asking!

you know it would probably take less time to fix this than I'm going to spend deleting and recreating these SLAs to et the right name ....  lets just fix this one 

Being a programmer myself, this sounds like a trivial modification!

We need this feature for consistency in our filters and Dashboard gadgets.  One of our projects has an SLA named differently from the other SLAs.

+1 for this feature.

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...