|↳||java.lang.Enum<E extends java.lang.Enum<E>>|
features provided by the application
|StandardFeature||ATTACHMENTS||Controls whether users can upload attachments in pull request comments.|
|StandardFeature||AUTH_CAPTCHA||Controls whether users will be required to solve a CAPTCHA after a configured number of failed attempts to login.|
|StandardFeature||COMMIT_GRAPH||Controls whether the commit graph is displayed on the commits page of a repository.|
|StandardFeature||DATA_CENTER_MIGRATION_EXPORT||Controls whether Data Center Migration archives can be generated on this instance.|
|StandardFeature||DATA_CENTER_MIGRATION_IMPORT||Controls whether Data Center Migration archives can be imported into the instance.|
|StandardFeature||DIAGNOSTICS||Controls whether diagnostics is enabled|
|StandardFeature||FILE_EDITOR||Controls whether users can edit repository files in the browser and via REST.|
|StandardFeature||FORKS||Controls whether repositories are allowed to be forked.|
|StandardFeature||GETTING_STARTED||Controls whether new users will be presented with a "Getting Started" page after their first login.|
|StandardFeature||PERSONAL_REPOS||Controls whether users can create repositories in their personal projects.|
|StandardFeature||PULL_REQUEST_DELETION||Controls whether pull requests can be deleted.|
|StandardFeature||SMART_MIRRORS||Controls whether smart mirrors can be configured.|
|StandardFeature||TIME_ZONE_ONBOARDING||Controls whether users will be prompted to update their timezone after their first login.|
|From interface com.atlassian.bitbucket.server.Feature|
Controls whether users can upload attachments in pull request comments. Disabling this feature will not delete any attachments that have already been uploaded, but will prevent uploading more.
Controls whether users will be required to solve a CAPTCHA after a configured number of failed attempts to login. Disabling this feature can reduce the overall security of an instance and is not recommended, but may be necessary in some environments. If this feature is disabled, it is strongly advised that some other aspect of the authentication mechanism (such as a remote LDAP directory) impose a limit on failed attempts in order to prevent attackers from using brute force attacks to compromise accounts.
Controls whether the commit graph is displayed on the commits page of a repository.
Controls whether Data Center Migration archives can be generated on this instance.
This is not a
data center-only feature, data can be exported from Server
installations as well.
Controls whether Data Center Migration archives can be imported into the instance.
This is a
data center-only feature.
Controls whether diagnostics is enabled
Controls whether users can edit repository files in the browser and via REST. Disabling this feature does not prevent plugins from using the Java API to edit files; it only disables editing via the UI and REST.
Controls whether new users will be presented with a "Getting Started" page after their first login.
Controls whether users can create repositories in their personal projects. Disabling this feature will
prevent creating new repositories in, or forking existing repositories to, users' personal projects.
To completely disable forking, regardless of the target project's type, the
FORKS feature should
be disabled instead of, or in addition to, this one.
Controls whether smart mirrors can be configured. This is a
data center-only feature.
Enabling or disabling this feature has no effect if a data center license is not installed. Disabling this
feature prevents the use of smart mirrors even if a data center license is installed.
Controls whether users will be prompted to update their timezone after their first login.