java.lang.Object | |
↳ | com.atlassian.jira.issue.fields.config.manager.FieldConfigManagerImpl |
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Retrieve field configuration by database ID.
| |||||||||||
Removes FieldConfig objects that are only associated to the specified FieldConfigScheme.
| |||||||||||
[Expand]
Inherited Methods | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
From class java.lang.Object | |||||||||||||||||||||
From interface
com.atlassian.jira.issue.fields.config.manager.FieldConfigManager
|
Retrieve field configuration by database ID.
configId | the database id |
---|
Removes 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.
fieldConfigSchemeId | the scheme id of the fieldConfigScheme the fieldConfigs are exclusive to. |
---|