Hi,

We cannot delete the custom SLA Fields automatically - please see JSD-183 for more details. However as matthew.omalley noted, in 2.0.2 we added the ability to clean up unused SLA fields. Please see https://confluence.atlassian.com/display/SERVICEDESK/Managing+SLA+data for info on how to do it.

Thanks,
Kat
JIRA Service Desk Team

I take that back - has everyone concerned seen this article:

https://confluence.atlassian.com/display/SERVICEDESK/Managing+SLA+data

Seems to be fixed in 6.3.5 where the SLA custom fields can be cleared via

Administration / Add ons / Service Desk / Configuration

seems to display all SLA custom fields which are not in use. These can be cleared.

Same issue here - would like this to be resolved.

This is an annoying bug which makes it difficult to determine which custom field is still used by the SLA and which not.
Make it difficult to work with and also an editable SLA would be fine which is not possible now.
If you create an SLA and misspelled it then you will have another custom field which annoys you.

Same issue here. I would appreciate an urgent fix.

Hi miruflin,

Just flagging this again. We now have over 80 service desks, and that means we've got around 80 people configuring their own service desks and creating SLA's. As we can't prevent users from creating new SLA custom fields (JSD-116) it would be really nice to tidy up the old ones as we consolidate them.

It's a game of whack-a-mole though until we get JSD-116 addressed.

Any update on addressing this, or workarounds you can suggest?

Thanks Michael, have a great day,
Nick

This is a serious issue affecting our ability to scale Service Desk, I welcome a fix.

Please consider also giving admins an option to prevent users from defining new SLA Custom Fields: JSD-116. There's already 21 created in our instance that all mean similar things.

Same problem