| Setting | Description |
| Allow users to vote on issues |
Controls whether voting is enabled in JIRA. Voting allows users to indicate a
preference for issues they would like to be completed or resolved. See also the
'View Voters and Watchers' permission.
Default: ON
|
| Allow users to watch issues |
Controls whether watching is enabled in JIRA. Users can 'watch' issues which they are interested in.
Users watching an issue will be notified of all changes to it. See also the
'View Voters and Watchers' and 'Manage Watcher List' permissions.
Default: ON
|
| Allow unassigned issues |
When turned ON, JIRA will allow issues to be unassigned or assigned to 'no-one'.
When turned OFF, issues must always be assigned to someone - by default,
the assignee will be the Project Lead as defined
for each project.
Default: OFF
|
| External user management |
When turned ON, JIRA will assume that you are managing users from outside JIRA (e.g.
using Crowd). This means that you will no longer be able to create, edit or
delete users/groups from within JIRA (or via email or import); but you can still assign users/groups to
project roles, and create/edit/delete
user properties.
Additionally, JIRA will not display options for users to change their password, or edit their
profile.
Note: JIRA's LDAP integration is currently limited to external
password management, so this option should be left OFF when using LDAP.
Default: OFF
|
| External password management |
When turned ON, JIRA will assume that you are managing passwords from outside JIRA.
JIRA will not display options for users to change their password, or display the 'Forgot Password'
link on the login screen.
Note: With the default osuser LDAP provider, this option should be
turned ON, as accounts are not yet stored in LDAP and this option only hides the
password features within JIRA.
Default: OFF
|
| Logout confirmation |
Controls whether to obtain user's confirmation when logging out.
cookie means prompt for
confirmation if the user was automatically logged in (via a cookie).
Default: NEVER
|
| Use GZip compression |
Controls whether to compress the web pages that JIRA sends to the browser. It is recommended that this be turned ON, unless you are using mod_proxy.
Default: OFF
|
| Allow remote API access |
Controls whether to allow remote client access (via XML-RPC or SOAP) to this JIRA installation for authenticated users.
Default: OFF
|
| User email visibility |
Controls how user email addresses are displayed in the user profile page.
PUBLIC — email addresses are visible to all.
HIDDEN — email addresses are hidden from all users.
MASKED — the email address is masked (e.g. 'user@example.com' is displayed as 'user at example dot com').
LOGGED IN USERS ONLY — only users logged in to JIRA can view the email addresses
Default: PUBLIC
|
| Comment visibility |
Determines what will be contained in the list that is presented to users when specifying
comment visibility and worklog visibility.
Groups & Project Roles — the list will contain groups and project roles.
Project Roles only — the list will only contain project roles.
Default: Project Roles only
|
| Exclude email header 'Precedence: bulk' |
Controls whether to prevent the Precedence: Bulk header on JIRA notification emails. This option should
only be enabled when notifications go to a mailing list which rejects 'bulk' emails. In normal circumstances,
this header prevents auto-replies (and hence potential mail loops).
Default: OFF
|
| Issue Picker Auto-complete |
Provides auto-completion of issue keys in the 'Issue Picker' popup screen.
Turn OFF if your users' browsers are incompatible with AJAX.
Default: ON
|
| User Picker Auto-complete |
Provides auto-completion of user names in the 'User Picker' popup screen.
Turn OFF if you have a very large number of users, or if your users' browsers are incompatible with AJAX.
Note: If 'User email visibility' (see above) is set to HIDDEN, the users' email addresses will not be searched
or shown in the auto-complete results.
Default: ON if you have less than 5,000 users (or OFF if you have more than 5,000 users).
|
