Documentation for JIRA 6.4 (This documentation includes the project navigation sidebar). Not using this? See below:
(JIRA 6.4 without sidebar documentation | JIRA 6.3.x documentation | JIRA Cloud documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

JIRA has a number of configuration options that allow your JIRA server to be customized for use within your organization. These options can be accessed and edited on JIRA's 'General Configuration' page.

On this page:

Editing JIRA's General Configuration

To access and edit options on the 'General Configuration' page:

  1. Log in as a user with the JIRA Administrators global permission.
  2. Choose > System. Select General Configuration to open the Administration page.
    (tick) Keyboard shortcut: g + g + start typing general configuration
  3. Scroll to the end of the page and click the Edit Configuration button to edit the three sections as described below:

(info) The Advanced Settings button is only visible if you have the JIRA System Administrators global permission.

General Settings




This is the title that will be displayed on the JIRA login page and the dashboard. It helps identify your installation and its purpose.
(info) Also see logo, which is displayed on every JIRA page.


JIRA can operate in two modes:
- Public — Anyone can sign themselves up with self-registration and create issues (within the bounds of your JIRA system's permissions).
- Private — Useful for internal issue-tracking systems where you do not want public users to login. Self-signup is disabled; only Administrators can create new users.
Default: Public

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).
Default: 3 (for new installations of JIRA)

(info) If you upgrade from a version of JIRA prior to 4.1.1, this option will be reset to 3 for security reasons mentioned in the JIRA 4.1.1 Upgrade Guide.

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.
Default: ON

Base URL

The base URL of this JIRA installation. (warning) 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 site. You cannot (for example) have a different hostname or URL for internal and external users. This is especially important for JIRA 4.0.x or higher, as any mismatch between this Base URL setting and the URL requested by your JIRA users will cause problems with dashboard gadgets. This URL is also used in outgoing email notifications as the prefix for links to JIRA issues.

Email from

Specifies the From: header format in notification emails. Default is of the form "John Doe (JIRA) <>". Available variables are '${fullname}', '${email}' and '${email.hostname}'. Note that the actual address (e.g. '') cannot be specified here

- it is determined by the mail server or individual project configuration



A short introduction message displayed on the dashboard. (info) Also see the announcement banner, which is displayed on every JIRA page. You can include HTML, but ensure all tags are correctly closed.




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.

(info) You will need to re-index JIRA if you change this value.

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 setting in their user profile. (To choose the time format see Configuring the Layout and Design.)

(info) Date fields, which 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) so are not affected by time zone settings.




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

Maximum project name sizeControls 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 sizeControls 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, 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.
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: OFF

Accept remote API calls

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 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. '' 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.

See JIRA Security Advisory 2008-08-26 for further details.

- 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 Administratorsglobal permission (not JIRA System Administrators - see JRA-27454 for details) will be notified as a result of this feature being used.
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. Users will not be able to use JIRA-specific avatars if Gravatars are enabled, and vice versa.
Default: OFF

Inline editEnables 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  

Product recommendationsEnables you to turn on/off recommendations for other Atlassian products on your JIRA site.
Default: ON
(info) Product recommendations are only displayed for JIRA OD evaluators (at this time).
Enable Atlassian analytics

Enables you to turn on/off Atlassian analytics

; see Data collection policy for more information

Default: OFF
(info) This option is not available for JIRA Cloud.




  1. It would be really nice to have a new option to force users to choose a "strong" password (e.g. over 8 characters and contains a number).  When selected, only strong passwords are accepted.

    1. Anonymous

      Yes please! Strong password option is very much needed.

      1. Seems to me an application like this should not require any password rules.  It would be nice for the application to allow the user to configure the password rules.  Because you want this, why force all that use JIRA to your opinion.  Make it configurable.

  2. Anonymous

    I don,t see how to change the Character encoding in Jira 4.4

    1. Hello there,

      This option was removed in JIRA 4.4. Furthermore, new installations of JIRA 4.4 consistently employ UTF-8 character encoding.

      The decision to remove this option was taken for:

      • Consistency — different languages (supported by JIRA) employed different character encodings in the past, whereas they now consistently employ UTF-8.
      • Simplicity — problems were caused when JIRA was switched to another language with a different character encoding.

      For more information about this change, please refer to JRA-19361 — in particular, the 2nd public comment on that issue.

      (info) The documentation above has been amended to reflect this change.


  3. I have Jira on a local network. So we can access it directly to the server or via the public IP.

    If I export to xml, I get either local or public IP in the links in that export, but I would like to change it so I always get the Public IP (since the local isn't usable outside the network).


    I have changed the base URL to the public IP, but that doesn't help,

  4. Anonymous

    I'm having issues after moving to Jira 4.4.1 from Jira 4.1.

    I'm using additional statement in the server.xml file in the <Connector> definition: scheme="https" proxyName="" proxyPort="443" and it works perfectly with SSL reverse-proxy. But then I get Jira as offline when trying to integrate it with Crucible. Can I simply add another <Connector> with scheme="http" and then specify internal server name and port when configuring Crucible?



  5. How do you change settings without being in the application for Standalone?  For example, I was trying out a different Base URL and now I can't log in because of the way JIRA is handling the Base URL and redirects.

  6. Please note that many of these features are inaccessible for JIRA OnDemand. Please see Restricted Functions in Atlassian OnDemand.

  7. Anonymous

    The base URL option is not used consistently. Jira 4.4.1 worked fine behind a reverse proxy where the proxy held the SSL certificate and the base URL reflected https URLs. Jira 5.0 does not, and it is a real PITA. Why such a difference? Yes, if you are wondering, I have preserve host on, and I have the reverse proxy configured correctly. It works fine for other things including Mercurial, MantisBT, Moin Moin, and other things. I even have a dotProject installation I slightly modified to do what it seemed Jira 4.4.1 did with the base URL correctly, and it still works fine. If you have a working Jira 4.4.1 and are using a reverse proxy, I would suggest hold off on upgrading and buying licenses for 5 until you have tested it out. Seriously.

  8. Anonymous

    I'm trying to figure out how to give a particular group in our JIRA system the rights to do Bulk Changes WITH the ability to turn off the email updates.  How would I go about doing this?  I cannot seem to find the right area to tell me how to do this...  thanks!

  9. Anonymous

    how i can modify a page with jtml?

  10. Anonymous


    'user picker' doesn't seem to work fine. When I try to configure a Mail handler, and I try to choose de Default reporter from an user picker control, I can´t pick any user. The suggestions appear when  I'm typing, and a window opens up to choose an user, but when a pick a name it doesn´t appear in the textbox.

    The permissions are set correctly because in other places this control works correctly.

    Is it a bug? Any workaround?

    Thanks in advance.

  11. A built-in option to configure the 'New User Welcome' email would be great to have. just something basic liek you get with SharePoint --text and maybe the option to attach document. 

    Then whenever we create a new JIRA user account, and select to send email notification for password and logon, it wodl also direct users to our company user introduction which contains details for Atlassian University, etc.

    I'd vote for that!

  12. how to reset the JIRA or confluence password in oracle sql


  13. JSN


    I'm using JIRA on Demand.

    Have a few users groups defined. Let's called them groupA groupB and groupC. That's in addition to the default jira-*, admin and site-admin groups.

    Have configured "Comment visibility" to "Groups & Project Roles".

    When I add a comment, inthe comment visibility list, I only see one of my many groups, say groupA.  groupB and groupC are not visible in the list.

    Any hint?






    1. JSN

      No one has ever had this problem?

      Maybe someone from Atlassian could take a crack at it...