Configuring advanced settings
Jira has a small number of commonly edited advanced configuration options, which are stored in the Jira database. These options can be accessed and edited from the Advanced Settings page. You must be a Jira System Administrator to do this.
Editing Jira's advanced settings
To access and edit options on the 'Advanced Settings' page:
- In the upper-right corner of the screen, select Administration
> System. - Click the Advanced Settings button on the 'General Configuration' page.
Edit the value of a Key by clicking its value on the right of the page and modifying the existing value.
The table below has extended information on some of the Key values.KeyKey configurationjira.attachments.number.of.zip.entries Configuring the number of files shown in the content of ZIP-format files on issues jira.clone.prefix Configuring the cloned issue summary field prefix jira.date.picker.java.format
jira.date.picker.javascript.format
jira.date.time.picker.java.format
jira.date.time.picker.javascript.formatConfiguring date picker formats jira.issue.actions.order Changing the default order for comments from ascending to descending jira.projectkey.pattern Changing the Project Key Format jira.search.views.default.max The default maximum number of issues exported from search results. Users can override the default by changing the URL tempMaxparameter. This value must always be lower than or equal to thejira.serach.views.max.limitvalue.jira.search.views.max.limit The absolute limit on the number of issues that can be exported from search results. jira.table.cols.subtasks Configuring sub-task fields displayed on parent issues jira.view.issue.links.sort.order Configuring the order of linked issues displayed on the 'view issue' page jira.text.field.character.limit This property limits the number of characters that can be entered into Description, Environments, Comments and text custom fields. The maximum is 2147483647. A value of 0 means unlimited characters. jira.comment.collapsing.minimum.hidden The minimum number of comments needed before the comment collapsing is enabled. jira.newsletter.tip.delay.days The number of days before a prompt to sign up to the Jira applications insiders newsletter is shown. A value of -1 disables this functionality. jira.bulk.create.max.issues.per.import This property allows you to set the maximum number of issues a user can import via CSV at one time. The maximum is 2147483647. Entering a value of 0 will disable the importer for users. jira.export.html.enabled Specifies whether users can export the JQL search results to HTML. jira.quicksearch.max.concurrent.searches The maximum number of concurrent searches that your users can perform by using the quick search. The limit applies to a single Jira instance (if you have Data Center with 5 nodes, the limit increases fivefold.)
Many concurrent searches will affect Jira's performance. You can use JMX monitoring to see how your users are searching, and determine the best limit.
crowd.encryption.encryptor.default This property defines password encryption algorithms:
DISABLED- disable the encryption. It’s an insecure option. We don’t recommend using it.BASE64- obfuscates passwords by encoding them with Base64. It’s an insecure option but it can be helpful in some cases. This option doesn’t require encryption keys. Learn more about backing up data.AES_CBC_PKCS5Padding- standard AES implementation in CBC mode. We recommend using this option.
com.atlassian.jira.issue.fields.usage.init.required This property is related to the custom field usage data that appears on the Custom fields page (the Last value update column). It lets you recalculate this data based on the information from the database, which is useful if the data is corrupt and you need to recalculate it from scratch. When you set the property to true, a one-time recalculation will be performed during the next run of the CustomFieldUsageRecalculationJob. You can check the details of this job by going to Scheduler details in the administration area. Once the recalculation is successful, the property is set back to false.- Click the Update button (which will appear in the Operations column on the right) to save the new value in the Jira database.
Please Note: - Any changes you make to these properties/keys become effective immediately.
- Click the General Settings button to return to the General Configuration page.
Related information
There are a handful of other advanced configuration options (which are of little interest to most Jira system administrators) whose default values can be customized in the jira-config.properties file located in the Jira application home directory, which you may want to edit. For details, please see Advanced Jira configuration.