Configuring JIRA
| 
PDF |
JIRA has a number of configuration options which can alter the way it operates, better customising the
application for your development team.
The current configuration can be viewed via the Administration interface. It should look like this:
Clicking Edit Configuration will allow you to edit the current configuration.
Here is a list of the different configuration options available, and what they do.
| Setting | Description |
| Title |
This is the title that will be shown to users logging into JIRA. It helps identify your installation and
its purpose. |
| Base URL |
This is the base URL of this Atlassian installation.
It is used in outgoing emails and notifications to construct valid links.
|
| Mode |
JIRA can operate in two modes:
| public |
The default operation mode for JIRA. Anyone can sign themselves up and create issues. |
| private |
Useful for internal issue tracking systems where you do not want public users to login. Signup is
disabled, only Administrators can create new users. |
|
| Attachment Path |
The absolute or relative path to the directory under which all attachments will be stored.
Note
When changing this path you will have to manually copy any existing attachments across to the new
directory.
|
| Introduction |
A short introduction message displayed on the dashboard. You can include HTML, but make sure to close all
your tags.
|
| Character Encoding |
The character encoding for input and viewing of information. For most western languages, the default
("UTF-8") is suitable.
If you change this setting - ensure that you also change your database's encoding.
View a list of supported encodings. However, please use the IANA preferred MIME name (such as 'iso-8859-1' instead of 'ISO8859_1') to
ensure XML backups have the correct encoding string.
|
| Allow users to vote on issues |
This controls whether or not users can vote for issues they want fixed.
Default: ON
|
| Allow users to watch issues |
Controls whether or not users can 'watch' issues that they are interested in. Users watching an issue
will be notified of all changes to it.
Default: ON
|
| Allow Attachments |
Controls if attachments are allowed. If turned on, you must enter an attachment path above.
Default: OFF
|
| Allow unassigned issues |
When turned on, JIRA will allow issues to be unassigned.
When turned off, issues will always be assigned to someone - when created this is by default the lead
project developer.
Default: OFF
|
| Allow assigning issues to new users |
When turned on, JIRA will allow issues to be assigned to an email address, a new developer will be
created automatically and a password emailed to the user.
When turned off, issues can only be assigned to existing developers.
Default: OFF
|
| Proactively cache projects / versions / components |
When turned on, JIRA will cache projects, versions & components.
As of JIRA 3.3 this caching is no longer needed, and should be turned off to save
memory.
Default: OFF
|
| External User Management |
When turned on, JIRA will assume that users are managed externally
- hence users cannot change their password or details from within JIRA.
Note that JIRA's LDAP integration is currently limited to external
password management, so this flag should be left OFF when using LDAP.
Default: OFF
|
There are a handful of other properties (usually storing defaults of little interest to most JIRA users) in the
WEB-INF/classes/jira-application.properties file, which you may want to edit.
