When you create a new SLA metric in a Service Desk a locked custom field is created for this SLA. But when i delete the SLA metric the custom field isn't deleted.

            [JSDSERVER-182] Created SLA Custom Fields doesnt get deleted

            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

            Katrina Walser (Inactive) added a comment - 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

            Ops added a comment -

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

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

            Ops added a comment - I take that back - has everyone concerned seen this article: https://confluence.atlassian.com/display/SERVICEDESK/Managing+SLA+data

            Thomas Herzog added a comment - - edited

            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.

            Thomas Herzog added a comment - - edited 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.

            Ops added a comment -

            Same issue here - would like this to be resolved.

            Ops added a comment - 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.

            Thomas Herzog added a comment - 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.

            Pieter Rousseau added a comment - Same issue here. I would appreciate an urgent fix.

            Nicholas Muldoon added a comment - - edited

            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

            Nicholas Muldoon added a comment - - edited 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.

            Dan McGarry added a comment - This is a serious issue affecting our ability to scale Service Desk, I welcome a fix.

            David Yu added a comment -

            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.

            David Yu added a comment - 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

            Jens Günzel added a comment - Same problem

            Mark Love added a comment -

            Same for me. Our Jira is littered with custom fields that the service desk module has created, but that we can't delete. These show up in lots of unhelpful places (e.g. on the search screen).

            We currently have 11 "Customer Request Type" custom fields, and it's impossible to know which are valid and which are redundant.

            We also have 4 SLA custom fields, despite only having 2 SLAs active in the live system.

            This module needs to clean up after itself, or help the user to.

            Mark Love added a comment - Same for me. Our Jira is littered with custom fields that the service desk module has created, but that we can't delete. These show up in lots of unhelpful places (e.g. on the search screen). We currently have 11 "Customer Request Type" custom fields, and it's impossible to know which are valid and which are redundant. We also have 4 SLA custom fields, despite only having 2 SLAs active in the live system. This module needs to clean up after itself, or help the user to.

            Patrick Guiran added a comment - - edited

            Hi Michael,

            I don't really understand your last sentence "The SLA shouldn't show for deleted metrics though, so please raise a separate bug report if that is the case.".

            In French, default SLA labels are quite long, which are not beautiful in reports and tables. I have deleted all default SLA metrics and have created mine ("SLA resolution", "SLA reply", etc..). The default ones are still there in "custom fields" and I can't delete them, even if they are not used at all in all projects of my Jira instance.

            How can I delete those unused fields ?

            Cheers,
            Patrick

            Patrick Guiran added a comment - - edited Hi Michael, I don't really understand your last sentence "The SLA shouldn't show for deleted metrics though, so please raise a separate bug report if that is the case.". In French, default SLA labels are quite long, which are not beautiful in reports and tables. I have deleted all default SLA metrics and have created mine ("SLA resolution", "SLA reply", etc..). The default ones are still there in "custom fields" and I can't delete them, even if they are not used at all in all projects of my Jira instance. How can I delete those unused fields ? Cheers, Patrick

            SLA fields don't get deleted currently as they are used across all projects.

            The SLA shouldn't show for deleted metrics though, so please raise a separate bug report if that is the case.

            Michael Ruflin (Inactive) added a comment - SLA fields don't get deleted currently as they are used across all projects. The SLA shouldn't show for deleted metrics though, so please raise a separate bug report if that is the case.

            Shane Froebel added a comment - - edited

            I can confirm this from JSD-183 that and old SLA is still showing on the issue even though I had deleted the SLA.

            I thought this was an issue, but I can not reproduce it anymore.

            Shane Froebel added a comment - - edited I can confirm this from JSD-183 that and old SLA is still showing on the issue even though I had deleted the SLA. I thought this was an issue, but I can not reproduce it anymore.

              Unassigned Unassigned
              06602615-a0fb-488e-912c-7decd1429c11 Deleted Account (Inactive)
              Affected customers:
              22 This affects my team
              Watchers:
              22 Start watching this issue

                Created:
                Updated:
                Resolved: