com.atlassian.jira.web.FieldVisibilityManager |
Known Indirect Subclasses |
This is an interface for the old FieldVisibilityBean. In the brave new world of OSGi and Plugins-2 we need an interface so it can proxied to the plugins. This allows it to be injected into Spring components.
Constants | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
String | ALL_ISSUE_TYPES |
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Checks if the custom field is hidden in the project with id of projectId.
| |||||||||||
Checks if the custom field is visible in the project with id of projectId.
| |||||||||||
Checks if the field is hidden across all the projects
that the user can see (has the
BROWSE permission). | |||||||||||
Checks if the field is hidden for the issue's current field layout scheme.
| |||||||||||
Checks if the field is hidden in the project with id of projectId.
| |||||||||||
Checks if specified field is hidden in at least one scheme associated with the specified project and issue type.
| |||||||||||
Checks if the field is hidden across all the projects
that the user can see (has the
BROWSE permission). | |||||||||||
Returns TRUE if specified field is hidden under the following scenarios:
1: Project specified - is field hidden in all schemes associated with the specified project. | |||||||||||
Checks if the field is visible in at least one of the projects
that the user can see (has the
BROWSE permission). | |||||||||||
Checks if the field is visible in the project with id of projectId.
| |||||||||||
Checks if the field is visible in at least one of the projects
that the user can see (has the
BROWSE permission). | |||||||||||
Checks if specified field is visible in all schemes associated with the specified project and issue type.
| |||||||||||
Checks if the field is visible for the issue's current field layout scheme.
|
Checks if the custom field is hidden in the project with id of projectId.
projectId | project id |
---|---|
customFieldId | the data store id of the custom field |
issueTypeId | issue type id |
Checks if the custom field is visible in the project with id of projectId.
projectId | project id |
---|---|
customFieldId | the data store id of the custom field |
issueTypeId | issue type id |
Checks if the field is hidden across all the projects
that the user can see (has the BROWSE
permission).
remoteUser | user |
---|---|
field | the field |
Checks if the field is hidden for the issue's current field layout scheme.
fieldId | field id |
---|---|
issue | issue |
Checks if the field is hidden in the project with id of projectId.
projectId | project id |
---|---|
fieldId | field id |
issueTypeId | issue type id |
Checks if specified field is hidden in at least one scheme associated with the specified project and issue type.
projectId | project id |
---|---|
fieldId | field id |
issueTypeId | issue type id |
Checks if the field is hidden across all the projects
that the user can see (has the BROWSE
permission).
remoteUser | user |
---|---|
id | the field ID |
Returns TRUE if specified field is hidden under the following scenarios:
1: Project specified - is field hidden in all schemes associated with the specified project.
2: Project and Issue Type(s) specified - is field hidden in all schemes associated with the specified project for the issue types specified.
Caching is abstracted to next level - all calls to getFieldLayout(...) are cached
projectId | project id |
---|---|
fieldId | field id |
issueTypes | list of issue type ids (as String objects) |
Checks if the field is visible in at least one of the projects
that the user can see (has the BROWSE
permission).
remoteUser | user |
---|---|
id | the field ID |
Checks if the field is visible in the project with id of projectId.
projectId | project id |
---|---|
fieldId | field id |
issueTypeId | issue type id |
Checks if the field is visible in at least one of the projects
that the user can see (has the BROWSE
permission).
remoteUser | user |
---|---|
field | the field |
Checks if specified field is visible in all schemes associated with the specified project and issue type.
projectId | project id |
---|---|
fieldId | field id |
issueTypeId | issue type id |
Checks if the field is visible for the issue's current field layout scheme.
fieldId | field id |
---|---|
issue | issue |