jira.ajax.autocomplete.issuepicker.enabled

true

boolean

false

jira.ajax.autocomplete.labelsuggestion.limit

uint

false

jira.ajax.autocomplete.labelsuggestion.timeout.ms

5000

uint

false

jira.ajax.autocomplete.limit AJAX Auto-complete Limit The maximum number of items to show when making suggestions for auto-complete. jira.ajax.autocomplete.limit.desc

uint

false

jira.issuenav.criteria.autoupdate Auto Update Criteria For supporting criteria updates search instantly jira.issuenav.criteria.update

true

boolean

true

false

jira.alertheader.visibility

private

enum

false

jira.assignee.change.is.sent.to.both.parties

true

boolean

false

jira.attachment.allow.zip.support

true

boolean

false

webwork.multipart.maxSize

10485760

uint

false

jira.attachment.do.not.expand.as.zip.extensions.list

docx, docm, dotx, dotm, xlsx, xlsm, xltx, xltm, xlsb, xlam, pptx, pptm, potx, potm, ppam, ppsx, ppsm, sldx, sldm, thmx, odt, odp, ods, odg, odb, odf, ott, otp, ots, otg, odm, sxw, stw, sxc, stc, sxi, sti, sxd, std, sxg

list<string>

false

jira.attachment.download.mime.sniffing.workaround

workaround

enum

false

jira.attachment.number.of.zip.entries Maximum number of zip entries to display The contents of zip attachments can be displayed, but often there are too many to display. jira.attachment.number.of.zip.entries.desc

uint

false

true

false

true

jira.autoexport

true

boolean

false

jira.avatar.megapixels

uint

false

jira.browser.unsupported.warnings.disabled

false

boolean

false

jira.bulk.edit.limit.issue.count

1000

uint

false

jira.chart.days.previous.limit.daily

300

uint

false

jira.chart.days.previous.limit.hourly

uint

false

jira.chart.days.previous.limit.monthly

7500

uint

false

jira.chart.days.previous.limit.quarterly

22500

uint

false

jira.chart.days.previous.limit.weekly

1750

uint

false

jira.chart.days.previous.limit.yearly

36500

uint

false

jira.clone.linktype.name

Cloners

string

false

jira.clone.prefix The prefix added to the Summary field of cloned issues

CLONE -

string

true

false

true

jira.comment.level.visibility.groups

false

boolean

false

dashboard.item.width.max Maximum width of a dashboard item

3840

uint

true

dashboard.item.height.max Maximum height of a dashboard item

2160

uint

true

jira.dashboard.max.gadgets

uint

false

jira.databasequery.batch.size

100

uint

false

jira.date.picker.java.format Date Picker Format (Java) This part is only for the Java (server side) generated dates. Note that this should correspond to the javascript date picker format (jira.date.picker.javascript.format) setting. jira.date.picker.java.format.desc

d/MMM/yyyy

com.atlassian.validation.SimpleDateFormatValidator string

true

false

true

jira.date.picker.javascript.format Date Picker Format (JavaScript) This part is only for the JavaScript (client side) generated dates. Note that this should correspond to the java date picker format (jira.date.picker.java.format) setting. jira.date.picker.javascript.format.desc

%e/%b/%Y

string

true

false

true

jira.date.time.picker.java.format DateTime Picker Format (Java) This part is only for the Java (server side) generated datetimes. Note that this should correspond to the javascript datetime picker format (jira.date.time.picker.javascript.format) setting. jira.date.time.picker.java.format.desc

dd/MMM/yyyy h:mm a

string com.atlassian.validation.SimpleDateFormatValidator

true

false

true

jira.date.time.picker.javascript.format DateTime Picker Format (JavaScript) This part is only for the JavaScript (client side) generated date times. Note that this should correspond to the java datetime picker format (jira.date.time.picker.java.format) setting. jira.date.time.picker.javascript.format.desc

%e/%b/%Y %I:%M %p

string

true

false

true

jira.default.jndi.name

java:comp/env/jdbc/JiraDS

string

false

jira.disable.login.gadget

false

boolean

false

jira.disable.multipart.get.http.request

true

boolean

false

jira.email.fromheader.format

${fullname} (Jira)

string

false

jira.export.fetchsize

-1

The number of items to fetch from the database into memory at a time. The default setting of -1 will stream the values on MySQL and use a fetch size of 1000 on other databases. uint

false

jira.exportimport.cleanxml

true

boolean

false

jira.home

string

false

jira.i18n.include.meta-data

true

boolean

false

jira.import.maxqueuesize

100

The maximum number of elements allowed on the queue before the XML parser waits for the database to catch up uint

false

jira.import.threads

How many threads to use for multi-threaded insertion of imported data uint

false

jira.index.batch.maxrambuffermb

1024

uint

false

jira.index.interactive.maxrambuffermb

1024

uint

false

jira.index.issue.maxqueuesize

4000

The maximum number of elements allowed on the queue before blocking on queue submission uint

false

jira.index.issue.minbatchsize

Minimum size of a batch that will cause the operation to become multi-threaded uint

false

jira.index.issue.threads

How many threads to use for multi-threaded indexing of issues uint

false

jira.index.sharedentity.maxqueuesize

4000

The maximum number of elements allowed on the queue before blocking on queue submission uint

false

jira.index.sharedentity.minbatchsize

Minimum size of a batch that will cause the operation to become multi-threaded uint

false

jira.index.sharedentity.threads

How many threads to use for multi-threaded indexing of shared entities (things that are favourited and/or shared) uint

false

jira.index.lock.waittime

30000

uint

false

jira.index.max.reindexes

2147483647

uint

false

jira.index.commitfrequency

30000

Index updates are written to disk at intervals of this many milliseconds. uint

false

jira.index.readerpooling

true

Enable this option to significantly reduce memory pressure induced by TermInfosReader on each index write. By default, IndexWriter does not pool the SegmentReaders it must open for deletions and merging, unless a near-real-time reader has been obtained. This method lets you enable pooling without getting a near-real-time reader (PERIODIC commit policy). boolean

false

jira.index.mergepolicy.forcemergedeletespctallowed

When forceMergeDeletes is called, we only merge away a segment if its delete percentage is over this threshold. Default is 10%. uint

false

jira.index.mergepolicy.floorsegmentmb

The TieredMergePolicy tries to merge together index segments that are roughly the same size. This setting tells it to ignore size differences for segments that are smaller than this, allowing all small segments to be candidates for merging. uint

false

jira.index.mergepolicy.maxmergeatonce

The maximum number of segment files that can be simultaneously merged into a single larger segment during normal internal merging. uint

false

jira.index.mergepolicy.maxmergeatonceexplicit

This value is used instead of jira.index.mergepolicy.maxmergeatonce when the merge is explicitly requested using IndexWriter.optimize or IndexWriter.expungeDeletes uint

false

jira.index.mergepolicy.maxmergedsegmentmb

5120

This is the largest size for any single segment of the index to reach. Lucene's default is 5120, which means 5GB segment files and slow merges so it is reduced, here. Setting it too low slows down searches and risks too many open files at once. uint

false

jira.index.mergepolicy.nocfspct

Controls what percentage of the total index size a segment can reach and still be a candidate for merging into the compound file format, which combines term dictionaries, frequencies, and so forth into a single file instead of individual ones. Smaller means more files and slower searching; larger means fewer but larger files and probably slower writes. uint

false

jira.index.mergepolicy.segmentspertier

A balancing factor that controls the number of segments that are permitted at each tier, meaning indexes that are roughly equivalent in size. With the default setting, it would be ok to have 9 segments that are 8MB each, but when a 10th is created, it would trigger 2 or more of them to be combined, which would move them up to a larger tier. uint

false

jira.index.mergepolicy.reclaimdeletesweight

2.0

Controls how aggressively merges that reclaim more deletions are favored. Higher values will more aggressively target merges that reclaim deletions. A value of 3.0 is probably nearly too high. A value of 0.0 means deletions don't impact merge selection. double

false

jira.index.mergepolicy.maxcfssegmentsizemb

Infinity

Controls the maximum compound file segment size. If a merged segment would be more than this value, it will be left as a non-compound file, even if jira.index.mergepolicy.usecompoundfile = true. double

false

jira.index.mergepolicy.usecompoundfile

false

An on/off switch for the use of the compound file format (compact index to use fewer file descriptors). boolean

false

jira.index.update.bulk.optimization

400

uint

false

jira.index.background.batch.size The number of issues to read from the database at once during background and foreground indexing.

4000

uint

false

true

false

true

jira.index.snapshot.count The number of index snapshots to retain.

uint

false

true

search.platform The search platform for search API, e.g. lucene, opensearch string

lucene

true

false

true

false

opensearch.index.issues.name The name of the OpenSearch index Jira will use for issues. string

jira-issues

true

false

true

false

opensearch.http.url The URL(s) of the OpenSearch cluster Jira will connect to. For Apache: A comma separated list of node URLs in the OpenSearch cluster. Can be a single URL. For AWS: A single Amazon OpenSearch domain host. string

true

false

true

false

opensearch.username The OpenSearch username when using basic authentication with the Apache transport. string

true

false

true

false

opensearch.password The OpenSearch password when using basic authentication with the Apache transport. string

true

false

true

false

opensearch.aws.region To use Amazon OpenSearch Service with request signing, set this property with the AWS region of the OpenSearch domain (for example, us-east-1). string

true

false

true

false

opensearch.stream.batch.size The batch size for streaming search results in OpenSearch. uint

500

true

false

true

false

opensearch.sorting.aggregate.request.page.size The request page size for OpenSearch used in sorting aggregations. uint

5000

true

false

true

false

opensearch.mget.batch.size The maximum number of documents to request in a single OpenSearch MGET request. uint

500

false

true

opensearch.http.request.compression.enabled Controls whether OpenSearch HTTP request compression is enabled. boolean

false

true

false

true

false

opensearch.http.connect.timeout OpenSearch HTTP client connection timeout in milliseconds. uint

5000

true

false

true

false

opensearch.http.request.connect.timeout OpenSearch HTTP client request connection timeout in milliseconds. uint

5000

true

false

true

false

opensearch.http.socket.timeout OpenSearch HTTP client socket timeout in milliseconds. uint

10000

true

false

true

false

opensearch.http.max.connection.total OpenSearch HTTP client max HTTP connections. uint

true

false

true

false

opensearch.http.max.connection.per.route OpenSearch HTTP client max HTTP connections per route. uint

true

false

true

false

opensearch.query.dfs.query.then.fetch OpenSearch request setting to enable DFS query then fetch. boolean

false

true

false

true

false

opensearch.force.refresh.on.write If enabled OpenSearch index will be refreshed on every write. Otherwise, Jira will apply a more relaxed index consistency: read-your-writes consistency. CAUTION: enable this if you are having issues related to delayed consistency, but note that doing so would negatively impact write performance. boolean

false

true

false

true

false

opensearch.max.result.buffer To config buffer size for OpenSearch responses when using Apache transport in binary (IEC) bytes. Default value is 104857600 bytes (100MB). uint

104857600

true

false

true

false

opensearch.rio.batch.size The batch size to use when performing replicated indexing operations to ensure the index is consistent. This value must be <= the index.max_terms_count setting on the issues index. The default is 65536 which is the default value of index.max_terms_count in OpenSearch. uint

65536

true

false

true

false

jira.search.api.reindex.processing.queue.size The size of the re-index processing queue. uint

4000

false

jira.search.api.reindex.producer.put.timeout.ms The timeout in milliseconds for the producer to put for new re-indexing tasks. uint

1000

false

true

jira.search.api.reindex.consumer.threads The number of consumer threads for re-indexing. uint

false

jira.search.api.reindex.consumer.poll.timeout.ms The timeout in milliseconds for the consumer to poll for new re-indexing tasks. uint

1000

false

true

jira.search.api.reindex.bulk.request.size The size of the bulk request sent to the search platform for re-indexing. uint

false

jira.search.api.reindex.failure.tolerance.percentage The percentage of failures tolerated during re-indexing before it is considered a failure. uint

false

jira.opensearch.max.payload.mb The maximum raw payload size for bulk index request payloads to OpenSearch. Differs from Lucene's default (48MB), because it's excessive for OpenSearch. Some AWS instance-types won't even allow HTTP requests >10MB. https://opensearch.org/docs/latest/tuning-your-cluster/performance/ recommends 5-15MiB as a starting point. uint

false

jira.search.platform.max.result.window The maximum number of results the underlying search platform will return. This is not the same as the maximum number of results that Jira will return, see jira.search.views.default.max. For Lucene, this will only be enforced if the Feature Flag "com.atlassian.jira.lucene.search.limit" is on. For OpenSearch, this will always be enforced. uint

10000

false

jira.search.lucene.stream.collector.thread.count The number of threads to use in the thread pool for streaming searches in Lucene. If significant degradation is experienced during search under heavy load this can be increased. uint

100

false

true

false

jira.issue.actions.order Jira issue actions order The default order of actions (tab items like 'Comments', 'Change History' etc) on the 'View Issue' screen, by date, from top to bottom. jira.issue.actions.order.desc

desc

true

false

true

jira.issueindex.fetch.size

200

uint

false

jira.lf.application.id

jira

string

false

jira.lf.date.relativize

true

boolean

false

jira.lf.date.time admin.globalsettings.lookandfeel.time.format

h:mm a

com.atlassian.jira.datetime.ExampleDateFormatOutputGenerator

com.atlassian.validation.SimpleDateFormatValidator string

false

true

jira.lf.date.day admin.globalsettings.lookandfeel.day.format

EEEE h:mm a

com.atlassian.jira.datetime.ExampleDateFormatOutputGenerator

com.atlassian.validation.SimpleDateFormatValidator string

false

true

jira.lf.date.complete admin.globalsettings.lookandfeel.complete.date.time.format

dd/MMM/yy h:mm a

com.atlassian.jira.datetime.ExampleDateFormatOutputGenerator

com.atlassian.validation.SimpleDateFormatValidator string

false

true

jira.lf.date.dmy admin.globalsettings.lookandfeel.day.month.year.format

dd/MMM/yy

com.atlassian.jira.datetime.ExampleDateFormatOutputGenerator

com.atlassian.validation.SimpleDateFormatValidator string

false

true

jira.date.time.picker.use.iso8061 admin.globalsettings.lookandfeel.date.time.picker.useISO8601 admin.globalsettings.lookandfeel.date.time.picker.useISO8601.description

false

boolean

false

true

jira.lf.gadget.color1 admin.globalsettings.lookandfeel.gadget.colour.color1

#0747a6

com.atlassian.validation.HexColourValidator colour

false

true

jira.lf.gadget.color2 admin.globalsettings.lookandfeel.gadget.colour.color2

#de350b

com.atlassian.validation.HexColourValidator colour

false

true

jira.lf.gadget.color3 admin.globalsettings.lookandfeel.gadget.colour.color3

#ff8b00

com.atlassian.validation.HexColourValidator colour

false

true

jira.lf.gadget.color4 admin.globalsettings.lookandfeel.gadget.colour.color4

#00875a

com.atlassian.validation.HexColourValidator colour

false

true

jira.lf.gadget.color5 admin.globalsettings.lookandfeel.gadget.colour.color5

#00a3bf

com.atlassian.validation.HexColourValidator colour

false

true

jira.lf.gadget.color6 admin.globalsettings.lookandfeel.gadget.colour.color6 com.atlassian.validation.HexColourValidator

#6554c0

colour

false

true

jira.lf.gadget.color7 admin.globalsettings.lookandfeel.gadget.colour.color7

#5e6c84

com.atlassian.validation.HexColourValidator colour

false

true

jira.lf.logo.height

uint

false

jira.lf.logo.url

/images/logos/light/jira-generic.png

string (url)

false

true

jira.lf.logo.dark.url

/images/logos/dark/jira-generic.png

string (url)

false

true

jira.lf.logo.show.application.title

false

boolean

false

true

jira.lf.logo.width

uint

false

jira.lf.favicon.url

/favicon.ico

string (url)

false

true

jira.lf.favicon.hires.url

/images/fav-jcore.png

string (url)

false

true

jira.lf.top.bgcolour admin.globalsettings.lookandfeel.top.bar.colour

#ffffff

com.atlassian.validation.HexColourValidator colour

false

true

jira.lf.top.hilightcolour admin.globalsettings.lookandfeel.top.bar.hilightcolour

#dddfe5

com.atlassian.validation.HexColourValidator colour

false

true

jira.lf.top.separator.bgcolor admin.globalsettings.lookandfeel.top.separatorcolor

#d8dce2

com.atlassian.validation.HexColourValidator colour

false

true

jira.lf.top.textcolour admin.globalsettings.lookandfeel.top.text.colour

#44546f

com.atlassian.validation.HexColourValidator colour

false

true

jira.lf.top.texthilightcolour Text Colour on Highlight in the header admin.globalsettings.lookandfeel.top.text.hilightcolour

#44546f

com.atlassian.validation.HexColourValidator colour

false

true

jira.lf.menu.bgcolour admin.globalsettings.lookandfeel.menu.bar.colour

#f1f2f4

com.atlassian.validation.HexColourValidator colour

false

true

jira.lf.menu.separator admin.globalsettings.lookandfeel.menu.bar.separator.colour

#dfe1e6

com.atlassian.validation.HexColourValidator colour

false

true

jira.lf.menu.textcolour admin.globalsettings.lookandfeel.menu.bar.text.colour

#44546f

com.atlassian.validation.HexColourValidator colour

false

true

jira.lf.hero.button.base.bg.colour admin.globalsettings.lookandfeel.herobutton.bg.colour

#0c66e4

com.atlassian.validation.HexColourValidator colour

false

true

jira.lf.hero.button.text.colour admin.globalsettings.lookandfeel.herobutton.text.colour

#ffffff

com.atlassian.validation.HexColourValidator colour

false

true

jira.lf.text.activelinkcolour admin.globalsettings.lookandfeel.link.active.colour

#0055cc

com.atlassian.validation.HexColourValidator colour

false

true

jira.lf.text.headingcolour admin.globalsettings.lookandfeel.heading.colour

#172b4d

com.atlassian.validation.HexColourValidator colour

false

true

jira.lf.text.linkcolour admin.globalsettings.lookandfeel.link.colour

#0c66e4

com.atlassian.validation.HexColourValidator colour

false

true

jira.max.AdminPage.history.items

uint

false

jira.max.history.items

uint

false

jira.max.issue.filter.dropdown.items

uint

false

jira.max.issue.history.dropdown.items

uint

false

jira.max.Issue.history.items

uint

false

jira.max.JQLQuery.history.items

uint

false

jira.maximum.authentication.attempts.allowed

uint

false

jira.xsrf.enabled XSRF security measures Controls whether XSRF (Cross-Site Request Forgery) security token protection is enabled in Jira. See http://en.wikipedia.org/wiki/Cross-site_request_forgery for more information. jira.xsrf.enabled.desc

true

boolean

false

jira.db.txns.disabled Database Transaction Support Controls the ability to turn off database transaction support. Only do so if directed to by Atlassian Support. jira.db.txns.disabled.desc

false

boolean

false

jira.option.allowcookies

true

boolean

false

jira.option.allowthumbnails

true

boolean

false

jira.option.emailvisible

show

enum

false

jira.option.ignore.url.with.key

true

boolean

false

jira.option.logoutconfirm

never

enum

false

jira.option.user.crowd.allow.rename Allow users to be renamed even when Jira is acting as a Crowd server Controls whether or not the ability to rename a user is enabled when Jira is configured to act as a Crowd server. Some client applications depending on Jira's Crowd server implementation may misinterpret a renamed user as having been deleted and created anew, in which case you can use this flag to disallow renames in Jira.

true

boolean

false

true

jira.option.auditing.log.retention.period.in.months For how many months should audit log entries be retained. Negative value means indefinitely

-1

string

false

jira.option.auditing.log.retention.period.last.change.timestamp Unix timestamp saying when the last change of auditing retention period was made. Value of zero means no change yet.

string

false

jira.project.summary.max.issues

uint

false

jira.projectkey.description

admin.projects.key.description

i18n ref

false

true

jira.projectkey.maxlength

uint

false

jira.projectkey.pattern Jira project key pattern A regular expression that defines a valid project key. jira.projectkey.pattern.desc

([A-Z][A-Z0-9]+)

com.atlassian.jira.project.ProjectKeyRegexValidator string

false

true

jira.projectkey.reservedwords.list

PRN, AUX, CLOCK$, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, CON, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9

list<string>

false

jira.projectkey.warning

admin.errors.must.specify.unique.project.key

i18n ref

false

jira.projectname.maxlength

uint

false

jira.releasenotes.default

Html

string

false

jira.releasenotes.templatenames

Html, Text

list<string>

false

jira.releasenotes.templates

releasenotes-html.vm, releasenotes-text.vm

list<string>

false

jira.schemes.comparison.max

uint

false

jira.screenshotapplet.enabled

true

boolean

false

jira.screenshotapplet.linux.enabled

false

boolean

false

jira.search.fullcontentview.pagebreaks

true

boolean

false

jira.search.maxclauses

65000

uint

false

jira.search.views.default.max Soft limit for the number of issues that can be exported The default maximum number of issues exported from search results. Users can override the default by changing the URL 'tempMax' parameter. This value must always be lower than or equal to the 'jira.search.views.max.limit' value. When set to '0' there is no default limit applied, but the value of 'jira.search.views.max.limit' still applies.

1000

uint

true

false

true

jira.search.views.max.limit Hard limit for the number of issues that can be exported This number sets the absolute limit on the number of issues that can be exported from search results. Users trying to request more get a 403 (Forbidden) HTTP error code. To disable, set to '-1'. After changing it, update the value of 'jira.search.views.default.max' to a value that is lower than or equal to this one.

1000

uint

true

false

true

jira.search.views.max.unlimited.group

string

false

jira.sendmail.recipient.batch.size

100

uint

false

jira.subscription.email.max.issues

200

uint

false

jira.table.cols.dashboard

issuetype, issuekey, summary, priority

list<string>

false

jira.table.cols.subtasks Jira subtasks table columns The columns to show when viewing sub-task issues in a table jira.table.cols.subtasks.desc

issuetype, status, assignee, progress

list<string> com.atlassian.jira.bc.admin.NavigableFieldListValidator

true

false

true

jira.table.cols.voted

issuetype, issuekey, summary, priority, status

list<string>

false

jira.table.cols.watched

issuetype, issuekey, summary, priority, status

list<string>

false

jira.table.gadget.max.rows

uint

false

jira.thumbnail.maxheight

200

uint

false

jira.thumbnail.maxwidth

200

uint

false

jira.thumbnails.scaling.factor

uint

false

true

false

jira.timetracking.copy.comment.to.work.desc.on.transition

true

boolean

false

jira.option.timetracking

false

boolean

false

jira.timetracking.days.per.week

uint

false

jira.timetracking.estimates.legacy.behaviour

true

boolean

false

jira.timetracking.format

pretty

enum

false

jira.timetracking.hours.per.day

uint

false

jira.timetracking.report.issues.limit

10000

uint

false

jira.title Jira application title

Jira

string

true

jira.upgrade.delay.minutes

uint

false

true

jira.upgrade.force.manual.schedule

false

boolean

false

true

jira.usermanagement.maxdisplaymembers

200

uint

false

jira.view.issue.links.sort.order Sort order for view issue links Specifies the sort order of the issue links on the 'View Issue' screen. jira.view.issue.links.sort.order.desc

type, status, priority

list<string> com.atlassian.jira.bc.admin.LinkSortFieldListValidator

true

false

true

jira.view.issue.show.quicksubtask.when.no.subtasks

false

boolean

false

jira.viewcvs.root.type

cvsroot

enum

false

jira.webresource.flushcounter

uint

false

jira.webresource.superbatch.flushcounter

uint

false

jira.websudo.is.disabled

false

boolean

false

jira.websudo.timeout

uint

false

user.default.share.private

true

boolean

false

user.issues.per.page

uint

false

user.keyboard.shortcuts.disabled

false

boolean

false

user.notifications.mimetype

html

string

false

user.notify.own.changes

false

boolean

false

user.show.actions.in.navigator

true

boolean

false

user.external.links.new.window

true

boolean

false

user.quicksearching.mode

smartquery

string

false

user.issue.comments.order

desc

false

jira.show.contact.administrators.form

false

boolean

false

true

show.plugin.marketing.hints

true

boolean

false

jira.enabled.dark.features

string

false

true

false

true

jira.text.field.character.limit The maximum number of characters to be entered for a single field. Affects Description, Environment, Comments and Text custom fields. 0 means unlimited.

32767

uint

false

true

false

true

jira.email.diff.max.characters The maximum number of characters that diff will be calculated for in email notifications. One-sentence message will be displayed for longer texts. 0 means unlimited.

10000

uint

false

true

false

true

jira.option.web.usegzip Enables or disables built-in GZIP compression for web requests

true

boolean

false

jira.mail.send.disabled Disables outgoing emails from Jira.

false

boolean

false

jira.mail.fetch.disabled Disables fetching incoming emails in Jira.

false

boolean

false

jira.search.stable.max.results The number of Issues to include in a stable search jira.search.stable.description

1000

uint com.atlassian.jira.bc.admin.StableSearchResultCountValidator

false

true

false

true

jira.search.cache.max.size The number of issues to keep in the browser cache jira.search.cache.max.size.description

uint com.atlassian.jira.bc.admin.ViewIssueMaxCacheSizeValidator

false

true

false

true

jira.comment.collapsing.minimum.hidden The minimum number of comments needing to be hidden for comment collapsing to occur. 0 means there will be no comment collapsing. jira.comment.collapsing.minimum.hidden.description

uint com.atlassian.jira.bc.admin.ViewIssueMinimumHiddenCommentsValidator

true

false

true

google.site.verification.key Verification key for Google Webmaster Tools google.site.verification.key.description

string

false

true

false

true

ops.bar.group.size.opsbar-transitions

uint

false

ops.bar.group.size.opsbar-admin

uint

false

jira.project.description.html.enabled

false

boolean

false

true

jira.rte.enabled

true

boolean

true

false

jira.custom.field.html.enabled

false

boolean

false

true

jira.user.avatar.gravatar.enabled

true

boolean

false

jira.security.level.permission.cache.max.size

256

uint

false

true

jira.project.and.user.to.security.level.cache.max.size Default maximum size for com.atlassian.jira.issue.security.IssueSecurityLevelManagerImpl.projectAndUserToSecurityLevelCache. If this value is set to 0, the cache size is unbounded.

300000

uint

false

true

jira.newsletter.tip.delay.days Delay in days before newsletter signup tip is shown The number of days before a prompt to sign up to the Jira Insiders newsletter is shown. A value of -1 disables this functionality. jira.newsletter.tip.delay.days.description

int

true

false

true

jira.bulk.create.max.issues.per.import Bulk Create max issues per import The maximum number of issues that can be created via a single file in CSV Importer available for non-administrators. 0 means non-admin CSV Importer will be disabled. bulk.create.max.issues.per.import.description

250

uint

true

false

true

onboarding.emails.server Server base URL to send onboarding emails

http://iris.stg.intsys.atlassian.com

string

false

jira.fullUserCache

true

boolean

false

true

jira.luceneUserSearcher

true

boolean

false

true

jira.internUserValues

false

boolean

false

true

jira.export.excel.enabled

false

boolean

false

true

jira.export.html.enabled Allow exporting table of issues as HTML Set to "false" to prevent users from exporting JQL search results to HTML table

true

boolean

true

false

true

jira.option.globalsharing

false

boolean

true

false

jira.quicksearch.max.concurrent.searches Quick search maximum number of concurrent searches The maximum number of concurrent searches that you can perform on a single Jira instance by using the quick search. jira.quicksearch.max.concurrent.searches.description

uint

true

false

true

jira.empty.jql.returns.no.data.enabled

false

boolean

true

false

jira.monitoring.jmx.enabled

true

boolean

true

admin.generalconfiguration.favourite.filters.jql.execution.timeout Maximum timeout of Favourite Filters gadget By default favourite filters gadget returns counts of the filters in it, sometimes it impacts performance. This settings allows admin to create global value ( for all users ) to restrict the time for filter to load. Default value is 5000 ms. string

5000

true

false

jira.csv.export.dialog.enabled

true

boolean

true

com.atlassian.jira.health.diagnostics.alerts.retention-period-days Diagnostics retention period days Number of days to retain Diagnostics Alerts

int

false

com.atlassian.jira.health.diagnostics.alerts.truncation-interval-days Diagnostics truncation job interval in days Number of days to run the truncation job

int

false

jira.diagnostics.thresholds.slow-query-millis Slow JQL query alert threshold Threshold in milliseconds defined for slow JQL query alerts.

5000

uint

false

jira.diagnostics.thresholds.number-of-results Number of results returned from JQL alert threshold Threshold in number of returned issues from a JQL query for JQL alerts.

1000

uint

false

jira.diagnostics.thresholds.query-complexity JQL query complexity alert threshold Query complexity alert threshold defined in number of Lucene query clauses.

10000

uint

false

jira.diagnostics.thresholds.query-custom-fields JQL query custom field alert threshold Threshold for number of custom fields returned from a JQL query for JQL alerts.

1000

uint

false

jira.diagnostics.settings.include-sql-in-alerts Include SQL in Alerts Settings to include potentially exposing SQL queries in diagnostic alerts

false

boolean

false

jira.diagnostics.threshold.database-pool-utilization Database pool utilization threshold Threshold for raising an alert on database pool utilization

double

false

jira.diagnostics.threshold.database-pool-utilization-time-window Database pool utilization time window Time window in minutes for tracking database pool utilization

int

false

jira.diagnostics.settings.database-pool-poller-interval Database pool poller interval Poller interval for database pool in seconds

int

false

jira.diagnostics.threshold.long-running-query Long running query threshold Threshold for length of long running database query for raising an alert in seconds

int

false

jira.diagnostics.settings.long-running-query-poller-interval Database long running query poller interval Poller interval for long running database queries in seconds

int

false

jira.diagnostics.settings.http-request-max-elapsed-time HTTP Request Max Elapsed time threshold Threshold for long running HTTP requests

int

false

jira.diagnostics.settings.scheduler-poller-interval Scheduler pool poller interval Poller interval for scheduler diagnostics in seconds

int

false

jira.diagnostics.threshold.scheduler-utilization-time-window Scheduler high utilization time window Time window in minutes for tracking high scheduler utilization

long

false

jira.diagnostics.perflog.poll.seconds Jira performance logging polling interval Polling interval in seconds defining how frequent performance metrics are logged to atlassian-jira-perf.log

uint

false

true

jira.diagnostics.ipdlog.poll.seconds Jira In-Product Diagnostics logging polling interval Polling interval in seconds defining how frequent In-Product Diagnostics metrics are logged to atlassian-jira-ipd-monitoring.log

uint

false

true

jira.diagnostics.thresholds.gc.warning.time-percentage GC diagnostics: time percentage warning threshold Threshold of the Old Gen garbage collection duration as a percentage of time. The warning GC diagnostic message will be logged if total time spent on garbage collection in the time window divided by the size of the time window exceeds this value.

20.0

double

false

true

jira.diagnostics.thresholds.gc.error.time-percentage GC diagnostics: time percentage error threshold Threshold of the Old Gen garbage collection duration as a percentage of time. The error GC diagnostic message will be logged if total time spent on garbage collection in the time window divided by the size of the time window exceeds this value.

50.0

double

false

true

jira.diagnostics.settings.gc.time-window-size-minutes GC diagnostics: time window size in minutes This ensures that the percentage of time spent on GC is calculated over longer period of time, which averages single spikes and makes sure alerts are raised only when high GC load persists. Setting it to e.g. 15 minutes means that current read of Garbage Collection statistics will be compared to a read that happened at least 15 minutes ago.

uint

false

true

jira.diagnostics.settings.gc.poller-interval-seconds GC diagnostics: poller interval Garbage collection time polling interval in seconds. Controls the interval of storing the consecutive GC statistics reads

uint

false

true

jira.diagnostics.settings.gc.include-top-allocations-in-alert-details GC diagnostics: include top allocations in alert details Controls whether information about threads that allocate the most memory should be included in alert details. This data may be useful in troubleshooting issues but harvesting it requires stopping the JVM which may affect application's performance.

false

boolean

false

true

jira.index.replication.maxretries How many times to retry a failed index replication operation. 0 means no operations will be retried.

uint

true

jira.filters.encoding.enforcer.excluded.mimes

text/plain;text/css;application/javascript;font/;image/;application/x-font

string jira.filters.encoding.enforcer.excluded.paths string com.atlassian.ratelimiting.whitelisted-url-patterns Rate limiting whitelist Comma-separated list of URL patterns that should not be affected by rate limiting. com.atlassian.ratelimiting.whitelisted-url-patterns.description

string

false

true

false

true

com.atlassian.ratelimiting.whitelisted-oauth-consumers Rate limiting whitelisted oauth consumer keys Comma-separated list of oauth consumer keys that should not be affected by rate limiting. com.atlassian.ratelimiting.whitelisted-oauth-consumers.description

string

false

true

false

true

jira.user.search.maxresults.limit The maximum number of users that can be returned by a search. A value lower than the number of users on the instance will lead to imprecise search results, while high values will lead to higher memory footprint of user searches (even if the actual number of users on the instance remains low).

2000000

uint

true

false

jira.user.management.browsable.results.limit The maximum number of users that can be browsed on user management view. The size bigger than 10000 is not recommended due to impact on rendering time.

10000

uint

true

false

true

cluster.task.cleanup.run.interval How often, in seconds, a cluster task cleanup service should run.

uint

false

true

cluster.task.cleanup.offline.node.threshold Threshold in minutes after which a node is considered offline by the cluster task cleanup service, allowing it to delete tasks from that node. The minimum allowed value is 10 (lower values will be overwritten by Jira).

uint

false

true

false

jira.entity.version.cleanup.deleted.retention.days Threshold in days after which the deleted versions will be cleaned. The default for this value is the same as default value for RETENTION_PERIOD of ReplicatedIndexCleaningService

uint

false

true

false

true

jira.jql.autocomplete.query.delay Delay in seconds that determines how much to wait for new keystrokes in JQL autocomplete before sending search request. This determines the frequency at which JQL autocomplete suggestions may submit requests. This setting is used only when JQL Auto-complete is enabled in System >> General Configuration.

0.3

double

false

true

jira.jql.autocomplete.min.query.length Min number of characters to be typed in JQL autocomplete query before suggestion search request is made. 0 means we start suggesting as soon as we type. This setting is used only when JQL Auto-complete is enabled in System >> General Configuration.

uint

false

true

jira.xsrf.dialog.display.url.params.enabled

false

boolean

false

true

crowd.encryption.encryptor.default Algorithm used to encrypt password stored in Embedded Crowd string com.atlassian.jira.crowd.embedded.encryptors.EncryptorPropertyValidator

false

true

false

true

jira.security.image.attachment.jwt.tokens.expiry.hours Adds a security token to every image attachment displayed in email notifications. This allows users to view images in their notifications within the expiry time, which is 168 hours (7 days) by default. Setting it to 0 disables the tokens, but users won’t see images at all.

168

long

false

true

com.atlassian.jira.issue.fields.usage.init.required Recalculates the custom fields usage data based only on the information from the database, and can be used as a fallback method. It’s a one-time recalculation, performed during the next run of the CustomFieldUsageRecalculationJob (see Scheduler details). Once it’s completed successfully, the property is set back to false.

true

boolean

true

false

true

com.atlassian.jira.issue.fields.usage.query.max.ids Maximum number of custom fields in one database query that retrieves custom field's usage information.

1000

int

true

false

true

false

com.atlassian.jira.issue.fields.usage.calc.date Information about last 'Issues with value' successful recalculation date.

null

String

true

false

jira.security.csp.sandbox.excluded.content.type Mime types which should not have Content-Security-Policy set to sandbox. Divided with semicolon.

string com.atlassian.jira.web.filters.steps.security.csp.CspSandboxContentTypeValidator

false

true

jira.security.csp.sandbox.included.content.disposition Content-Disposition types which should have Content-Security-Policy set to sandbox (inline, attachment or both). Divided with semicolon.

attachment

string com.atlassian.jira.web.filters.steps.security.csp.CspSandboxContentDispositionValidator

false

true

jira.issue.view.comment.reactions.enabled

true

boolean

true

jira.option.stacktraceOnErrorpage boolean

true

false

true

false

jira.security.csp.sandbox.browser.differentiated.clauses Adds additional clauses to responses containing CSP sandbox header. It should be specified like "BROWSER:clause;BROWSER:clause". Supported browsers are: "EDGE_LEGACY_DESKTOP", "FIREFOX_DESKTOP", "CHROME_DESKTOP", "CHROME_IOS", "CHROME_ANDROID", "SAFARI_DESKTOP", "SAFARI_IOS", "ANDROID", "OTHER". It is related to issues with audio/video attachments playback in Chrome and Safari: https://jira.atlassian.com/browse/JRASERVER-72275.

CHROME_DESKTOP:allow-same-origin;CHROME_ANDROID:allow-same-origin;CHROME_IOS:allow-scripts;SAFARI_DESKTOP:allow-scripts;SAFARI_IOS:allow-scripts

string com.atlassian.jira.web.filters.steps.security.csp.CspSandboxBrowserDifferentiationValidator

false

true

jira.security.csp.sandbox.browser.differentiated.paths Paths which should have different Content-Security-Sandbox sandbox policies set, to workaround their bugs. Servlet paths should be divided with semicolons. It is related to issues with audio/video attachments playback in Chrome and Safari: https://jira.atlassian.com/browse/JRASERVER-72275. string

false

true

jira.security.duplicated.user.accounts List of users, who should have duplicated user accounts. If you are sure that this is needed please specify usernames as a list divided by ampersands. Otherwise please deactivate not needed accounts. Related JAC ticket: https://jira.atlassian.com/browse/JRASERVER-68797 string com.atlassian.jira.user.util.DuplicatedUsersPropertyValidator

false

true

false

true

jira.safeguards.issue.comments.enabled Enable or disable the issue comments safeguard. When disabled, no comment limits will be enforced. boolean

true

false

true

jira.safeguards.issue.comments A DC-only setting to define the maximum number of comments that can be added to any issue in the Jira instance. To maintain an instance's performance, we recommend a value of 1000. The value of "-1" will disable the limit. For this to take effect, also configure the "jira.safeguards.config.restricted.groups" setting. Once the limit is set, Jira will start sending notifications when the limit is breached or close to being breached. For more information about the impact on those user accounts and recommended limits, see the Safeguards documentation: https://docs.atlassian.com/jira/jadm-docs-0900/Configuring+Safeguards int

1000

true

false

true

jira.safeguards.config.restricted.groups A DC-only configuration of a comma separated list of groups for which the safeguards limitations are enforced. This means that users included in these groups will have their actions blocked in the case of a limit breach. A default value of no group ("") implies no group is being limited. We recommend including in the group the accounts used for automation and artificial content generation (bot accounts). For this to take effect, also configure the "jira.safeguards.issue.comments" setting. For more information about the processing and the impact on the instance, see the Safeguards documentation: https://docs.atlassian.com/jira/jadm-docs-0900/Configuring+Safeguards list<string>

true

false

true

jira.safeguards.rest.issue.comments.page The maximum number of embedded comments per issue via REST API: /rest/api/2/ISSUE-KEY. The maximum comments per page via REST API: /res/api/2/ISSUE-KEY/comment. int

1000

true

false

true

jira.safeguards.webhooks.issue.comments.page The maximum number of comments that can be provided in webhooks for an issue. int

100

true

false

true

jira.safeguards.custom.fields.enabled Enable or disable the custom fields safeguard. When disabled, no custom field limits will be enforced. boolean

false

true

false

true

jira.safeguards.custom.fields A DC-only setting to define the maximum number of custom fields allowed in the Jira instance. To maintain an instance's performance, we recommend a value of 1200. Once the limit is set, Jira will start sending notifications when the limit is breached or close to being breached. For more information about the impact on those user accounts and recommended limits, see the Safeguards documentation: https://docs.atlassian.com/jira/jadm-docs-0900/Configuring+Safeguards int

1200

true

false

true

jira.safeguards.issue.types.enabled Enable or disable the issue types safeguard. When disabled, no issue type limits will be enforced. boolean

false

true

false

true

jira.safeguards.issue.types A DC-only setting to define the maximum number of issue types allowed in the Jira instance. To maintain an instance's performance, we recommend a value of 250. Once the limit is set, Jira will start sending notifications when the limit is breached or close to being breached. For more information about the impact on those user accounts and recommended limits, see the Safeguards documentation: https://docs.atlassian.com/jira/jadm-docs-0900/Configuring+Safeguards int

250

true

false

true

jira.safeguards.issues.enabled Enable or disable the issues safeguard. When disabled, no issue limit will be enforced. boolean

false

true

false

true

jira.safeguards.issues A DC-only setting to define the maximum number of issues allowed in the Jira instance. To maintain an instance's performance, we recommend a value of 18M. Once the limit is set, Jira will start sending notifications when the limit is breached or close to being breached. For more information about the impact on those user accounts and recommended limits, see the Safeguards documentation: https://docs.atlassian.com/jira/jadm-docs-0900/Configuring+Safeguards int

18000000

true

false

true

jira.safeguards.projects.enabled Enable or disable the projects safeguard. When disabled, no project limit will be enforced. boolean

false

true

false

true

jira.safeguards.projects A DC-only setting to define the maximum number of projects allowed in the Jira instance. To maintain an instance's performance, we recommend a value of 7000. Once the limit is set, Jira will start sending notifications when the limit is breached or close to being breached. For more information about the impact on those user accounts and recommended limits, see the Safeguards documentation: https://docs.atlassian.com/jira/jadm-docs-0900/Configuring+Safeguards int

7000

true

false

true

jira.project.permission.helper.beta.fix.enabled

false

boolean

true

jira.project.permission.helper.beta.fix.enabled

false

boolean

true

jira.permission.cache.size The number of permission records to keep in project permissions cache.

1000

uint

true

jira.integrity.checker.results.limit The maximum number of records to fix in one integrity check.

1000

int

true

false

true

jira.integrity.checker.workflow.current.step.batch.size The maximum number of issues in single issue batch used in workflow current steps integrity checker.

1000

int

true

false

jira.integrity.checker.displayable.results.limit The maximum number of results listed for a single integrity check.

int

true

false

true

jira.jmx.strict.admin.permissions Controls whether Jira requires stricter permissions for managing JMX monitoring. When enabled, administering JMX monitoring and exposing the collected metrics requires SYS_ADMIN permissions.

false

boolean

false

true

false

true

jira.feature.flags.strict.admin.permissions Controls whether Jira requires stricter permissions for editing feature flags (dark features). When enabled, enabling or disabling certain dark features requires SYS_ADMIN permissions.

false

boolean

false

true

false

true

jira.index.recovery.from.relative.path.only Controls whether the Jira index recovery feature requires specifying a file path relative to the index snapshots directory in the Jira Home folder. If disabled, you can provide an absolute file path to the snapshot.

false

boolean

false

true

false

true

jira.index.synchronized.index.snapshot.restoration Controls whether the Jira index recovery is synchronized across the cluster or if multiple nodes can start recovery operation at the same time.

true

boolean

false

true

false

true

jira.clause.count.limit Maximum number of clauses allowed in a query to prevent out-of-memory errors.

65000

int

false

true

false

true

jira.clause.count.estimation Defines if the estimation of an index search query clause count is enabled or not.

true

boolean

false

true

false

true