Class FieldConfigManagerImpl
java.lang.Object
com.atlassian.jira.issue.fields.config.manager.FieldConfigManagerImpl
- All Implemented Interfaces:
FieldConfigManager
-
Constructor Summary
ConstructorsConstructorDescriptionFieldConfigManagerImpl(FieldConfigPersister configPersister, FieldConfigCleanup fieldConfigCleanup) -
Method Summary
Modifier and TypeMethodDescriptioncreateFieldConfig(FieldConfig newConfig, List<FieldConfigItemType> configurationItemTypes) getFieldConfig(Long configId) Retrieve field configuration by database ID.voidremoveConfigsForConfigScheme(Long fieldConfigSchemeId) Removes FieldConfig objects that are only associated to the specified FieldConfigScheme.updateFieldConfig(FieldConfig newConfig)
-
Constructor Details
-
FieldConfigManagerImpl
public FieldConfigManagerImpl(FieldConfigPersister configPersister, FieldConfigCleanup fieldConfigCleanup)
-
-
Method Details
-
getFieldConfig
Description copied from interface:FieldConfigManagerRetrieve field configuration by database ID.- Specified by:
getFieldConfigin interfaceFieldConfigManager- Parameters:
configId- the database id- Returns:
- the FieldConfig object
-
createFieldConfig
public FieldConfig createFieldConfig(FieldConfig newConfig, List<FieldConfigItemType> configurationItemTypes) - Specified by:
createFieldConfigin interfaceFieldConfigManager
-
createWithDefaultValues
- Specified by:
createWithDefaultValuesin interfaceFieldConfigManager
-
updateFieldConfig
- Specified by:
updateFieldConfigin interfaceFieldConfigManager
-
removeConfigsForConfigScheme
Description copied from interface:FieldConfigManagerRemoves FieldConfig objects that are only associated to the specified FieldConfigScheme. In theory, a FieldConfig should only ever be associated to one FieldConfigScheme, but here we take a defensive approach.When FieldConfig objects are removed, their associated OptionSets and GenericConfigs are also removed.
Note that the mapping from FieldConfig to FieldConfigScheme in FieldConfigSchemeIssueType is not removed until FieldConfigScheme#remove() is called. Thus, if someone calls FieldConfigSchemeManager#getFieldConfigScheme() after this method is called but before the FieldConfigScheme is removed, a NullPointerException will occur because the FieldConfig referenced by the mapping record no longer exists.
- Specified by:
removeConfigsForConfigSchemein interfaceFieldConfigManager- Parameters:
fieldConfigSchemeId- the scheme id of the fieldConfigScheme the fieldConfigs are exclusive to.
-