Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-15464

Deleting custom fields used in Request types leaves information in the Jira database that should be removed

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 3.0.0, 4.0.0, 5.0.0, 5.17.2

      Problem

      Deleting a custom field does not remove it from the "AO_54307E_VIEWPORTFIELD" table, which holds the fields for the JSM Request Types.

      Suggested Solution

      When removing a custom field that is not in use anymore, any reference to it should also be removed from the database

      Why This Is Important

      Although no apparent issue or loss of functionality is noticed within Jira itself, some third-party apps such as Project Configurator may be impacted by those "orphaned" references and throw errors in the logs as below:

      2024-07-23 15:49:57,873-0300 JiraTaskExecutionThread-3 ERROR user     [c.a.projectconfigurator.projectconfigserialize.ProjectConfigSerializingContext] [Project ITP] [Service desk ITP] [Request Type Desktop/Laptop support@@Service Request]  Trying to export Request Type found problem: Could not find object: Field with ID 'customfield_10900' used by Request Type 'Desktop/Laptop support'
      com.awnaba.projectconfigurator.utils.errorhandling.ObjectNotFoundException: Could not find object: Field with ID 'customfield_10900' used by Request Type 'Desktop/Laptop support'

      Workaround

            [JSDSERVER-15464] Deleting custom fields used in Request types leaves information in the Jira database that should be removed

            Tim Hailey added a comment -

            Jira should remove all references to a custom field when deleting custom fields from the Jira UI. Jira Admins should not have to take Jira down and manually remove this information from the Jira database.

            Tim Hailey added a comment - Jira should remove all references to a custom field when deleting custom fields from the Jira UI. Jira Admins should not have to take Jira down and manually remove this information from the Jira database.

              Unassigned Unassigned
              489dcb58d5d9 Edson Araujo
              Affected customers:
              5 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated: