Details
-
Bug
-
Resolution: Fixed
-
High
-
3.11
-
3.11
-
Description
Steps to reproduce the bug:
- Create a new Issue Type (Defunct Issue Type)
- Create a new Custom Field (Bad Custom Field) and configure it to be enabled for Defunct Issue Type
- Delete Bad Custom Field
- 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)
Attachments
Issue Links
- causes
-
JRASERVER-14256 NPE on custom field deletion
- Closed
- is related to
-
JRASERVER-14010 Integrity Checker should be updated to check for deleted custom fields in FieldConfiguration
- Closed
- relates to
-
JRASERVER-10461 Deleting an issue type breaks custom fields that had used it
- Closed