NullPointerException thrown when deleting an Issue Type which was configured for a non-existent Custom Field

XMLWordPrintable

    • 3.11

      Steps to reproduce the bug:

      1. Create a new Issue Type (Defunct Issue Type)
      2. Create a new Custom Field (Bad Custom Field) and configure it to be enabled for Defunct Issue Type
      3. Delete Bad Custom Field
      4. Attempt to delete Defunct Issue Type - a 500 error page is displayed with a NullPointerException. Stack trace looks something like this:
      java.lang.NullPointerException
	at com.atlassian.jira.issue.fields.config.persistence.FieldConfigPersisterImpl.getFieldConfig(FieldConfigPersisterImpl.java:118)
	at com.atlassian.jira.issue.fields.config.persistence.FieldConfigSchemePersisterImpl.transformToDomainObject(FieldConfigSchemePersisterImpl.java:248)
	at com.atlassian.jira.issue.fields.config.persistence.FieldConfigSchemePersisterImpl.getFieldConfigScheme(FieldConfigSchemePersisterImpl.java:176)
	at com.atlassian.jira.issue.fields.config.persistence.CachedFieldConfigSchemePersister.getFieldConfigScheme(CachedFieldConfigSchemePersister.java:54)
	at com.atlassian.jira.issue.fields.config.persistence.FieldConfigSchemePersisterImpl.getInvalidFieldConfigSchemeAfterIssueTypeRemoval(FieldConfigSchemePersisterImpl.java:113)
	at com.atlassian.jira.issue.fields.config.manager.FieldConfigSchemeManagerImpl.getInvalidFieldConfigSchemesForIssueTypeRemoval(FieldConfigSchemeManagerImpl.java:289)
	at com.atlassian.jira.issue.fields.config.manager.FieldConfigSchemeManagerImpl.removeInvalidFieldConfigSchemesForIssueType(FieldConfigSchemeManagerImpl.java:273)
	at com.atlassian.jira.web.action.admin.issuetypes.DeleteIssueType.doExecute(DeleteIssueType.java:181)

            Assignee:
            Unassigned
            Reporter:
            Michael Tokar
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: