Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-36798

Unable to delete field configuration created by plugin e.g. Service Desk

XMLWordPrintable

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      Symptoms

      Currently, it's not possible to delete or remove any field configuration in JIRA, as there isn't any delete button for it, even if the 'field config' is not used anywhere.

      Steps to reproduce
      1. Run a vanilla JIRA 6.2.3 and install Service Desk 1.2.5
      2. Create a new Service Desk Project
      3. Navigate to project Administration and disable Service Desk
      4. Remove Field Configuration Scheme for the newly created project. (There will be duplicated Field Configuration Scheme due to JSD-467)
      5. Navigate to Field Configuration. The option to delete field configuration is not available.
      Workaround

      You can delete a field configuration by calling the URL:

      JIRA OnDemand
      https://<instance-name>.atlassian.net/secure/admin/DeleteFieldLayout!default.jspa?id=111
      JIRA Installed
      http://<base-url>/secure/admin/DeleteFieldLayout!default.jspa?id=10201

      Where (id) is the ID of the field configuration, which you can obtain it by hovering your mouse over the field config and you will see the ID at the bottom of your browser.

        1. sd1.png
          sd1.png
          60 kB

            [JRASERVER-36798] Unable to delete field configuration created by plugin e.g. Service Desk

            Oswaldo Hernandez (Inactive) added a comment -

            Hi all,

            Several engineers have tried to reproduce this issue independently in recent versions of JIRA Service Desk and have been unable to reproduce the issue described here.

            Consequently, I am going to proceed to resolve this as Obsolete If you are able to reproduce this again, please raise it with us in a support case at https://support.atlassian.com so we can investigate further.

            Thanks.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi all, Several engineers have tried to reproduce this issue independently in recent versions of JIRA Service Desk and have been unable to reproduce the issue described here. Consequently, I am going to proceed to resolve this as Obsolete If you are able to reproduce this again, please raise it with us in a support case at https://support.atlassian.com so we can investigate further. Thanks. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            Benjamin Peikes added a comment -

            Still an issue.

            Benjamin Peikes added a comment - Still an issue.

            Matthew Goddard added a comment -

            This is still an issue on Jira 6.3.15 and Service Desk 2.3.0.

            Matthew Goddard added a comment - This is still an issue on Jira 6.3.15 and Service Desk 2.3.0.

            Harsha Yalamanchili added a comment -

            Confirmed on Jira 6.2.4 and Service Desk 1.2.6.1 - This is still an issue.

            Harsha Yalamanchili added a comment - Confirmed on Jira 6.2.4 and Service Desk 1.2.6.1 - This is still an issue.

            Oswaldo Hernandez (Inactive) added a comment -

            Hi romar,

            Could you please add detailed steps to reproduce here? I have tried creating and deleting field configs from the UI and it works as expected.

            Oswaldo Hernandez (Inactive) added a comment - Hi romar , Could you please add detailed steps to reproduce here? I have tried creating and deleting field configs from the UI and it works as expected.

            ɹǝʞɐq pɐɹq added a comment -

            No magic on our side. We do create a field configs but they are 100% vanilla. If we cant delete then its a JIRA bug

            ɹǝʞɐq pɐɹq added a comment - No magic on our side. We do create a field configs but they are 100% vanilla. If we cant delete then its a JIRA bug

            Oswaldo Hernandez (Inactive) added a comment -

            bbaker Is this intentional? I know you can't delete the Default Field Configuration but you can regularly delete user created ones. Does SD have magic to prevent user to mess with its field configurations?

            Thanks mate.

            Cheers,
            Os.

            Oswaldo Hernandez (Inactive) added a comment - bbaker Is this intentional? I know you can't delete the Default Field Configuration but you can regularly delete user created ones. Does SD have magic to prevent user to mess with its field configurations? Thanks mate. Cheers, Os.

              Unassigned Unassigned
              romar Abdulrazaq Mohammed Ali Omar (Inactive)
              Affected customers:
              15 This affects my team
              Watchers:
              21 Start watching this issue

                Created:
                Updated:
                Resolved: