Configuring Jira application options
Editing Jira's general configuration
- From the top navigation bar select Administration
> System. - Select General Configuration to open the Administration page.
- Click the Edit Settings button to edit the three sections as described below:
The Advanced Settings button is only visible if you have the Jira System Administrators global permission.
General settings
(If marked with an * the function is not available or editable in the Cloud)
Setting | Description |
|---|---|
Title | This is the title that will be displayed on the Jira login page and the dashboard. It helps identify your installation and its purpose. |
Mode * | Jira can operate in two modes:
|
Maximum Authentication Attempts Allowed * | The maximum authentication attempts that are allowed before CAPTCHA is shown to a user. If you leave it blank then CAPTCHA will never be shown and users will have unlimited authentication attempts. It is recommended that you set this to a small number (e.g. below 5). |
CAPTCHA on signup * | If you are running Jira in Public mode (see above), it is strongly recommended that you enable CAPTCHA. This will show a CAPTCHA image on signup to prevent spambots from signing up. |
Base URL* | The base URL of this Jira installation. You can only configure Jira to respond to a single URL and this setting must match the URL that your users request for accessing your Jira instance. You cannot (for example) have a different hostname or URL for internal and external users. This URL is also used in outgoing email notifications as the prefix for links to Jira issues.Check out Configuring the base URL for more information. |
Email from | Specifies the From: header format in notification emails. Default is of the form "John Doe (Jira) <jira@company.com>". Available variables are '${fullname}', '${email}' and '${email.hostname}'. Note that the actual address (e.g. 'jira@company.com') cannot be specified here. The address is determined by the mail server or individual project configuration. |
Introduction | A short introduction message displayed on the dashboard. |
Internationalization
Setting | Description |
|---|---|
| Indexing language | Jira uses Lucene, a high-performance text search engine library, in full-text searches for issues stored in Jira. This option is designed to enhance Jira's search indexing and issue searching features for issues entered in the languages available in this list. Hence, choose the language that matches the language used in your issues. Choosing a specific language in this list has the following effects when conducting searches in Jira (with respect to your chosen language):
If multiple languages are used in your issues (or you wish to disable the two effects above), choose Other.
|
| Installed languages | This section lists all language packs available within the Jira system.(Note: to install additional languages, see Internationalization.) |
| Default language | The language used throughout the Jira interface (as selected from the list displayed in Installed Languages above).Users can override the default language by using the Language setting in their user profile. |
| Default user time zone | This is the time zone used throughout the Jira interface. Users can override the default time zone by using the Time Zone preference in their user profile. (To choose the time format, see Configuring the look and feel of your Jira applications.) Date fields that have no time component, such as due dates, release dates (associated with versions), and custom date fields, solely record date information (and no time zone-related information). These are not affected by time zone settings. |
Options
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. For Jira Service Management, you can additionally enable voting for requests in the customer portal. For more info, see Managing access to your service project. 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 users to share dashboards and filters with the public | Controls whether "Public" is an option for sharing a filter. Users can choose who to share a filter with, and "Public" allows them to share it with anonymous users i.e. user not logged into Jira. If your instance can be accessed publicly, these filters will be accessible by the general public. Changing the option to OFF will not change any existing filters that are shared as "Public". Default: ON |
| Maximum project name size | Controls the maximum number of characters allowed for a project name. Changing this value will not affect the names of existing projects. Default: 80 |
| Maximum project key size | Controls the maximum number of characters allowed for a project key. Changing this value will not affect the keys of existing projects. You can set this to any value between 2 and 255, inclusive. Default: 10 |
| Allow unassigned issues | When turned ON, the default assignee for the project is Unassigned. 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: ON |
| External user management | When turned ON, Jira will not display options for users to change their password and edit their profile. This will also disable the Forgot your password link on the login page.Generally you would only turn this ON if you are managing all your users from outside Jira (e.g. using Crowd, Microsoft Active Directory, or another LDAP directory)Default: OFF |
| Logout confirmation | Controls whether to obtain user's confirmation when logging out: NEVER COOKIE - prompt for confirmation if the user was automatically logged in (via a cookie). ALWAYS 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: ON |
| User email visibility | Controls how users' 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 |
| JQL Auto-complete | Provides auto-completion of search terms when users perform an advanced (JQL) search. Turn OFF if you prefer not to use this feature, or are experiencing a performance impact. Default: ON |
| Internet Explorer MIME Sniffing Security Hole Workaround Policy | Attachment viewing security options for cross-site site scripting vulnerabilities present in Internet Explorer 7 and earlier. Changes the default browser action for attachments in Jira. Options are: - Insecure: inline display of attachments - allows all attachments to be displayed inline. Only select this option if you fully understand the security risks. - Secure: forced download of all attachments for all browsers - force the download of all attachments. This is the most secure option, but is less convenient for users. - Work around Internet Explorer security hole - forced download of high-risk attachments (IE-only Workaround) - for IE browsers, force the download of attachments that IE would mistakenly detect as an HTML file. Declared HTML attachments are also never displayed inline. Use this option to reduce the risk of attacks to IE users via attachments. Default: Work around Internet Explorer security hole |
| Contact Administrators Form | Provides an email form for users to fill in when they click the 'Contact Administrators' link (which appears when appropriate in Jira, e.g. on Login panels and pages). Applies only if outgoing email is enabled. Can be used with or without the custom 'Contact Administrators Message' below. Users with the Jira Administrators global permission (not Jira System Administrators - see JRA-27454 for details) will be notified as a result of this feature being used. To learn more on how to configure the form, see Configuring the administrator contact form. Default: OFF |
| Contact Administrators Message | Displays a custom message when users click the 'Contact Administrators' link (which appears when appropriate in Jira, e.g. on Login panels and pages). The 'Contact Administrators Message' will be displayed at the top of the 'Contact Administrators Form', only if the form is enabled (see above). |
| Allow Gravatars | Enables users to use Gravatars in their user profile instead of Jira-specific avatars. Default: OFF |
| Inline edit | Enables inline editing, i.e. click to edit a field on the screen. Default: ON |
| Auto-update search results | Enables search results to be automatically updated when criteria are modified in a basic search. Default: ON |
| Enable HTML in custom field descriptions and list item values | Allows to add HTML to the descriptions of custom fields and the values of list items. Default: OFF (recommended for security) |
| Disable empty JQL queries | Allows you to choose how an empty JQL query behaves: either returning no results at all (ON), or all existing issues (OFF). We've introduced this option to avoid performance issues with empty filters returning all existing issues in your instance. Note that some apps may be using empty JQL queries to return all issues on purpose. Turning on this option will affect them. An empty JQL query in Queues, SLAs and Reports within Jira Service Management will continue to return all issues per project. Default: OFF |
| Enable extra options when exporting to CSV | Allows you to choose a delimiter when exporting your search results to a CSV file. When exporting, you can choose to separate the values with one of these delimiters:
If you turn off this option, comma (,) will be used as the default delimiter. It's useful if you're making a lot of exports and don't want the extra dialog to be displayed every time. Default: ON |
| Max timeout of Favorite Filters gadget | The Favorite Filters gadget shows a list of favorite filters and the number of issues each of them contains. This option allows you to set the max timeout after which Jira stops counting the issues and instead displays the "Too many issues" message next to the filter. If you have large filters, counting the issues takes time and might affect Jira performance, so use this option to avoid that. Default: 5000 (ms) If you set it to -1, Jira won’t be counting issues at all. |
| Display URL parameters in security dialogs (8.12.1+) | If disabled, the setting prevents URL parameter values from being captured and displayed on security dialogs such as the session or XSFR token expiry dialogs. This is to prevent possible phishing attacks and tackle security vulnerabilities. Default: OFF |