com.atlassian.jira.issue.fields.config.manager.FieldConfigSchemeManager |
Known Indirect Subclasses |
Fields | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
ALL_ISSUE_TYPES | This magic value list contains a single null element. |
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Returns a non-null list of Projects associated with the given field.
| |||||||||||
Retrieves the
FieldConfigScheme associated with the
FieldConfig | |||||||||||
Returns a collection of
FieldConfigScheme s for all Configuration
Contexts that will become invalid after the issuetype has been removed. | |||||||||||
Returns the relevant field config of this custom field for the give issue context
| |||||||||||
This method is deprecated.
Use
getRelevantConfigScheme(Project, ConfigurableField) instead. Since v6.3.7.
| |||||||||||
Returns the FieldConfigScheme for the given Project and ConfigurableField.
| |||||||||||
Returns true if the custom field has a config for the Project and Issue Type of the given IssueContext.
| |||||||||||
Removes a field config scheme, as well as its associated contexts and field configs
(which includes option sets and generic configs)
| |||||||||||
Given a CustomField, this method will correctly remove the fieldConfigSchemes if necessary.
| |||||||||||
Given an issueType, this method will correctly remove the fieldConfigSchemes if necessary.
| |||||||||||
Updates the config schemes with the new contexts
| |||||||||||
Only update the name & description of a field
|
This magic value list contains a single null element. Do not change to an empty list.
Returns a non-null list of Projects associated with the given field.
field | the Field |
---|
Retrieves the FieldConfigScheme
associated with the
FieldConfig
fieldConfig | the field config to retrieve the FieldConfigScheme of; cannot be null. |
---|
FieldConfig
. Null if the config scheme can not be found.
Returns a collection of FieldConfigScheme
s for all Configuration
Contexts that will become invalid after the issuetype has been removed. That is the configuration contexts that
will no longer be linked to ANY issue types after the issue type passed is has been deleted.
issueType | The issueType to be deleted |
---|
FieldConfigScheme
sReturns the relevant field config of this custom field for the give issue context
issueContext | issue context to find the relevant field config for |
---|
This method is deprecated.
Use getRelevantConfigScheme(Project, ConfigurableField)
instead. Since v6.3.7.
Returns the FieldConfigScheme for the given Project and ConfigurableField.
issueContext | actually we ignore the Issue Type and just use the Project. |
---|---|
field | the ConfigurableField |
Returns the FieldConfigScheme for the given Project and ConfigurableField.
project | the Project. |
---|---|
field | the ConfigurableField |
Returns true if the custom field has a config for the Project and Issue Type of the given IssueContext.
This is equivalent to calling
getRelevantConfig(issueContext, field) != nullbut in general can run faster because it does not have to resolve the actual FieldConfig.
issueContext | IssueContext whose project and issue type will be used to check if the field has a config |
---|
Removes a field config scheme, as well as its associated contexts and field configs (which includes option sets and generic configs)
fieldConfigSchemeId | the id of the field config scheme to remove |
---|
Given a CustomField, this method will correctly remove the fieldConfigSchemes if necessary. In other words if a FieldConfigScheme is linked to only a single CustomField, and we're deleting that field then that FieldConfigScheme will be deleted. If a FieldConfigScheme is associated with multiple fields, then only the association for the field we're deleting will be removed, but the FieldConfigScheme will remain.
customFieldId | The id of the CustomField being deleted |
---|
Given an issueType, this method will correctly remove the fieldConfigSchemes if necessary. In other words if a FieldConfigScheme is linked to only a single issueType, and we're deleting that issuetype then that FieldConfigScheme will be deleted. If a FieldConfigScheme is associated with multiple issueTypes, then only the association for the issueType we're deleting will be removed, but the FieldConfigScheme will remain.
issueType | The IssueType being deleted |
---|
Updates the config schemes with the new contexts
Only update the name & description of a field
scheme | scheme with the name & description to be updated |
---|