# This file contains defaults for application properties
#
# The keys must match up with the keys found in APKeys.java
#
# NB - the values in this file are not automatically
# handed to the application.  The special call
# ApplicationProperties().getDefaultBackedString()
# will return the values in this file if they are not found
# in the database

jira.title = JIRA

#
# This controls the LOGO images used by JIRA
#
jira.lf.logo.url = /images/jira_logo_small.png
jira.lf.logo.width = 111
jira.lf.logo.height = 30

#
# These are the background and foreground colors of
# the top half of the header banner
#
jira.lf.top.bgcolour =  #114070
jira.lf.top.textcolour = #f0f0f0

#
# These are the background and foreground hilight colors of
# the top half of the header banner
#
jira.lf.top.hilightcolour =  #325c82
jira.lf.top.texthilightcolour = #ffffff

#
# This is the image used to indicate that a link is in fact a drop
# down menu.  The size of this image is crucial and it must be 7x4
#
jira.lf.top.menuindicatorimage = ../images/menu_indicator_for_dark_backgrounds.gif

#
# This is the color of the menu separator, a small line
# between the top and bottom sections of the header banner
#
jira.lf.top.separator.bgcolor = #003366

#
# These are the background and foreground colors of
# the bottom half of the header banner, eg the
# menu section
#
jira.lf.menu.bgcolour = #3c78b5
jira.lf.menu.textcolour = #ffffff

#
# These are the background and foreground hilight colors of
# the bottom half of the header banner, eg the
# menu section
#
jira.lf.menu.highlightcolour = #ffffff
jira.lf.menu.texthighlightcolour = #114070

#
# These are the colors of the hyperlinks in JIRA
#
jira.lf.text.linkcolour = #003366
jira.lf.text.activelinkcolour = #660000

#
# This is the color of JIRA page headings
#
jira.lf.text.headingcolour = #003366

#
# This is the color of the border around the drop down menu box
jira.lf.menu.dropdown.bordercolour = #bbbbbb

jira.option.logoutconfirm = never

# By default we want to receive trackbacks, but not send them
jira.option.trackback.send = false
jira.option.trackback.receive = true

jira.lf.date.time = hh:mm a
jira.lf.date.day = EEEE hh:mm a
jira.lf.date.complete = dd/MMM/yy hh:mm a
jira.lf.date.dmy = dd/MMM/yy
# Whether to display dates relative to now, eg. 'Today, 2:12pm'
jira.lf.date.relativize = true

# allowed values for format are "pretty", "hours", "days"
jira.timetracking.format=pretty
jira.timetracking.hours.per.day=24
jira.timetracking.days.per.week=7

# Set this to higher than your expected number of issues, if you want date range searches across all issues to work. See JRA-3127
jira.search.maxclauses=65000

# Whether to include pagebreaks between issues in the full content view. Setting to 'true' may break old Mozilla-based browsers - see JRA-4226
jira.search.fullcontentview.pagebreaks = true

# if you want to override your jvm locale uncomment the line below
# jira.i18n.default.locale = en_US

# The locale used when sorting database results. Defaults to 'jira.i18n.default.locale' if not specified.
#
# There are times when JIRA has to sort database results itself instead of using the database.  This setting
# controls the JIRA side sorting.  This setting should be as close as possible to the sorting locale that
# the database is using.
#
# We don't expect you to set this property unless directed to by JIRA support.
#
# jira.i18n.sql.locale = en_US

#
# This property controls the java.text.Collator that is used when JIRA does database result search itself.
#
# These string values are derived from the constants that apply to the java.text.Collator.setStrength() method.  You can
# read more information about these values here at :  http://java.sun.com/javase/6/docs/api/java/text/Collator.html
#
# We don't expect you to set this property unless directed to by JIRA support.
#
#jira.i18n.sql.collator.strength = PRIMARY
#jira.i18n.sql.collator.strength = SECONDARY
#jira.i18n.sql.collator.strength = TERTIARY
#jira.i18n.sql.collator.strength = IDENTICAL

# These two properties need to match for the datepicker to perform correctly
# The first date is in Java format
# (http://java.sun.com/j2se/1.4.2/docs/api/java/text/SimpleDateFormat.html).
# The second in unix format (see the FORMAT section of http://unixhelp.ed.ac.uk/CGI/man-cgi?date)
# Please note that the following options are not recognised: %c %D %E, %F, %G, %g, %h %r %R %T %x %X %z %Z - _ ^ #
# After editing ensure the date picker creates valid dates, we also recommend you make this format the same as Day/Month/Year Format
# in the administration section of JIRA
jira.date.picker.java.format = d/MMM/yy
jira.date.picker.javascript.format = %e/%b/%y

# These two properties need to match for the datetime picker to perform correctly
# The first date is in Java format
# (http://java.sun.com/j2se/1.4.2/docs/api/java/text/SimpleDateFormat.html).
# The second in unix format (see the FORMAT section of http://unixhelp.ed.ac.uk/CGI/man-cgi?date)
# Please note that the following options are not recognised: %c %D %E, %F, %G, %g, %h %r %R %T %x %X %z %Z - _ ^ #
# After editing ensure the date time custom field picker creates valid dates
jira.date.time.picker.java.format = dd/MMM/yy hh:mm a
jira.date.time.picker.javascript.format = %e/%b/%y %I:%M %p

# These list the templates that can be used for generating changlogs.
# For each template, there needs to a corresponding entry in *both* properties
jira.releasenotes.templatenames = Text, Html
jira.releasenotes.templates = releasenotes-text.vm, releasenotes-html.vm

# By default, we should enable thumbnails
jira.option.allowthumbnails=true

# Whether to show the 'Remember my login on this computer' checkbox on login.
# Storing cookies is conceivably a security risk if users frequently use shared computers
jira.option.allowcookies=true

# Thumbnail width and height params for creating thumbnails
# If you change this value, then you need to delete the thumbnails ('*_thumb_*') currently stored on disk
jira.thumbnail.maxwidth=200
jira.thumbnail.maxheight=200

# If you would like to disable the screenshot applet set this property to false
jira.screenshotapplet.enabled=true

# The number of attachment boxes to show on the attach file screen
jira.attachment.number = 3

# The prefix added to the summary of cloned issues and the clone linktype name
jira.clone.prefix = CLONE -
jira.clone.linktype.name = Cloners

# Project Key Pattern
# Specify the perl5 regexp for defining the project key - this regex will be prepended with "^" and closed with "$" for an exact matching rule.
# Note that the project key must only be allowed to contain ASCII characters, as it is used in HTTP GET requests.  This means that
# you should not allow slashes (/) in your project keys, as they will make it impossible for JIRA to distinguish between
# project keys and unrelated URL parts.  See http://jira.atlassian.com/browse/JRA-12819.  Hyphens should also be excluded.  See http://jira.atlassian.com/browse/JRA-13910 for more information.
#
# Also specify the warning and description that will be displayed to inform the user how the project key should be formed.
#
# If you wish to have alphaNumeric project keys, use the pattern:  ([A-Z][A-Z0-9]+)
jira.projectkey.pattern = ([A-Z][A-Z]+)

# Uncomment the following option if you'd like to revert back to the old issue key detection behaviour.
# For more info see http://jira.atlassian.com/browse/JRA-12354
#
#jira.option.key.detection.backwards.compatible=true

# The 2 properties below use the i18n packages to obtain the project key warning and description
# However it is still possible change the text here. For example, the below will still work:
# jira.projectkey.warning = This is a test warning!
jira.projectkey.warning = admin.errors.must.specify.unique.project.key
jira.projectkey.description = admin.projects.key.description

# If this is true, JIRA will removed invalid characters during an import
# WARNING: Don't enable under Tomcat in 3.0-beta, as it breaks things
jira.exportimport.cleanxml = true

# 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}
# If commented out, format is just 'jira@company.com'.
jira.email.fromheader.format = ${fullname} (JIRA)

#The maximum number of issues that can be sent in an individual e-mail subscription. A value of -1 can be used to
#indicate there is no limit.
#
# WARNING: Setting to -1 can cause JIRA to run out of memory if there is a subscription with a large number of
#  issues.

jira.subscription.email.max.issues=200

# Set the encoding to use in outgoing emails
# jira.i18n.email.encoding = UTF-8

# Auto Export
# Configure if auto export occurs on upgrade
jira.autoexport=true

# HTML header to put across the top of all pages (if set).  This can be used to communicate system wide information
#jira.alertheader =
# Set the visibility of the HTML alert header. values are: 'public' (show to anyone) or 'private' (show to logged in users only)
jira.alertheader.visibility=private

# The default order of actions (tab items like comments, change history etc) on the view issue screen, by date, from top to bottom
# Possible values are: asc desc
jira.issue.actions.order=asc

# A prefix for the custom field that links to the old issue for imported issues (eg Mantis / Bugzilla)
# Bugzilla example:
# jira.importid.prefix = http://localhost/bugzilla/show_bug.cgi?id=
# Mantis example:
# jira.importid.prefix = http://localhost/mantis/bug_view_advanced_page.php?bug_id=
# Commenting out this property will render the ID non-linked.
# Special (default) value 'unconfigured' notifies the admin that the property needs configuring
jira.importid.prefix = unconfigured

# Option determining how user email addresses are displayed on the profile page
# The options are "show", "mask", "hide", "logged-in"
jira.option.emailvisible = show

# Option to control the maximum number of issue records that will be retrieved in one database 'OR' query
# A larger value should lead to better performance, however will consume more database resources
# Please ensure the database has enough resources to handle large 'OR' queries if you are increasing this value
jira.databasequery.batch.size = 100

# Option to set how many issues to fetch at once for re-indexing
# This number of issues is fetched at once from the database & re-indexed.
# This option limits the amount of memory used by JIRA whilst re-indexing
jira.issueindex.fetch.size = 200

# Option specifying the CVS root type to pass when accessing ViewCVS
# Example ViewCVS URL: http://viewcvspath/viewcvs.cgi/path?<CVS ROOT _TYPE>=cvs_root
# Valid CVS root types are:
# 1. cvsroot
# 2. root
jira.viewcvs.root.type=cvsroot

# Specifys the default values for user preferences
# notifcation mimetype preference, html or text emails
user.notifications.mimetype=text
# number of issues per issue navigator page
user.issues.per.page=50
# does the user want to be notified about their own changes on watched issues
user.notify.own.changes=true
# Are filters and dashboards shared with everyone (public) by default
user.default.share.private=true

# A space/comma separated list of reserved words that cannot be used as key-words
# Please see JRA-8051 for more information.  Generally this is a list of keywords
# that are reserved, and cannot be used for creating directories on the filesystem
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

# Controls the maximum number of users that will be displayed for a group when
# managing user membership in bulk
jira.usermanagement.maxdisplaymembers = 200

# Option specifying if a string containing URLs with a JIRA Key on the end
# should be considered to contain a JIRA Key.
# Set to true to ignore keys on the ends of URLs
# Set to false to include keys on the ends of URLs
jira.option.ignore.url.with.key=true

# Should we show the form for creating subtasks in the parent issue even when there are no subtasks yet?
jira.view.issue.show.quicksubtask.when.no.subtasks=false

# Specifies the sort order of the issue links on the view issue screen.
# The value is a comma seperated list of 'key', 'type', 'status', 'priority' or 'resolution'
jira.view.issue.links.sort.order = type, status, priority

# The columns to view when viewing issues in a table.  The values that you can put
# here are valid values from IssueFieldConstants.
jira.table.cols.linkedissue = issuetype, issuekey, summary, status, priority

# The columns to view when viewing issues in a table.  The values that you can put
# here are valid values from IssueFieldConstants.
# Note that the summary field is put in by default, as it uses a different summary field to normal
jira.table.cols.subtasks = issuetype, status, assignee, progress

# This template formats the sub-task quick creation form that appears on the View Issue page.
# Horizontal and vertical forms are provided (vertical works better if fields need labels or use textareas)
jira.subtask.quickcreateform.template = templates/jira/issue/subtask/quickcreationform-vertical.vm
#jira.subtask.quickcreateform.template = templates/jira/issue/subtask/quickcreationform-horizontal.vm

# The fields to show on the sub-task quick creation form that appears on the View Issue page
# The values must be valid issue field ids (see IssueFieldConstants class) and can contain custom fields
# The issue field id may be followed by the label text or an i18n message key for the label, separated by colon (':').
# This will be used to display the label for this field if horizontal template is selected.
# The format of the custom field is 'customfield_<id>' where <id> is the numeric id of the field in the database
# Field values may be preset, eg. 'summary,issuetype=7,assignee=-1' where only 'summary' would show.
jira.subtask.quickcreateform.fields = summary,issuetype,assignee,timetracking

# Specified the 'wait time' for a file lock in the Lucene IssueIndexManager (in milliseconds)
# This value should only be modified if you are seeing a jira.issue.index.DefaultIndexManager 'Giving up reindex' ERROR
# in your log files or requested to do so by Atlassian support.
jira.index.lock.waittime=30000

# Number of issue index updates before automatic index optimization is triggered.
# A value of 0 indicates never trigger.
jira.index.max.reindexes=4000

# Number of issue indexes performed in bulk that will trigger index optimization.
# A value of 0 indicates never trigger.
jira.index.update.bulk.optimization=400

#--------------------------------------------------------------------------------------------
# Lucene IndexWriter settings
#--------------------------------------------------------------------------------------------

# Maximum number of Terms (words) that will be indexed for each field (eg. Issue Description or Environment)
jira.index.maxfieldlength = 10000

## Note: cannot set maxmergedocs any higher than 2147483647 as that is the MAXIMUM value for an integer

#
# Batch mode
#

jira.index.batch.mergefactor = 50
jira.index.batch.maxmergedocs = 2147483647
jira.index.batch.maxbuffereddocs = 300

#
# Intereactive mode
#

jira.index.interactive.mergefactor = 4
jira.index.interactive.maxmergedocs = 2147483647
jira.index.interactive.maxbuffereddocs = 300

#--------------------------------------------------------------------------------------------

# Setting for comment visibility level for project roles and groups
# true = Both Groups and Project Roles enabled
# false = groups disabled
jira.comment.level.visibility.groups=false

# Setting for how many schemes you can run a comparison against at one time. This should stay at or around 5 as
# the tool presents far too much information as the number goes up.
jira.schemes.comparison.max=5

# The number of recipients to send in each email when using the 'send bulk email' function in JIRA.
jira.sendmail.recipient.batch.size=100

# A counter that signifies the last time that static web resources were flushed
jira.webresource.flushcounter=1

# Number of results to display in the AJAX autocomplete pickers
jira.ajax.autocomplete.limit=20

# Whether or not ajax issue picker is enabled
jira.ajax.autocomplete.issuepicker.enabled = true

# The max number of users that can be used with AJAX user picker
jira.ajax.autocomplete.userpicker.limit = 5000

##
# The maximum number of results to issue navigator will request from a query
# - set this to zero or negative to be unrestricted (note that the server may forbid this, see below)
#
jira.search.views.default.max = 1000

# Limits the number of issues that may be edited via a bulk operation in one go.
# This may be useful if you are experiencing performance issues due to a large number of concurrent edits of
# large number of issues.  Please note that this should NOT be used to disable bulk edit operations.  Use the
# Global 'Bulk Change' permission accessible via the Admin interface in JIRA to do this.
# If a user tries to edit more than the provided number of issues here, an error will be displayed.
# Set the count to a negative number (-1) or simply comment out this property for unlimited number of issues.
#jira.bulk.edit.limit.issue.count = 100

##
# Whether search results are capped to a hard limit, otherwise return a 403 (Forbidden) to the client.
#
# Set this to negative (-1) or empty for unlimited results.
#
# NOTE: this SHOULD BE EQUALS OR GREATER THAN than jira.search.views.default.max above, otherwise all issue navigator links will fail with a 403
#
#jira.search.views.max.limit =

##
# Regardless of the above, users in this group will be able to request search requests that are unlimited.
#
# This MUST be a valid group or empty.
#
#jira.search.views.max.unlimited.group =

# This property is a workaround for http://jira.atlassian.com/browse/JRA-13791.  If this property is set to true,
# JIRA will only try to handle multipart POSTs.  Multipart GETs will be ignored by the mulipart request handler.
# If the property is commented out or set to false, JIRA will also try to handle multipart GETs however,
# this may lead to a problem due to a bug in Safari, where a GET may be submitted with the multipart content-type
# header even though it isn't needed.
jira.disable.multipart.get.http.request=true

#-----------------------------------------------------------------------------------------------------------------------
# Trusted Applications
#-----------------------------------------------------------------------------------------------------------------------

#
# Default URL matches (the URLs that TrustedApplications are allowed to access must START WITH the urls in the URL Match)
#
# Note: use '\n' as a delimiter between multiple urls so they appear on different lines
#
jira.trustedapps.urlmatch.default=/sr/jira.issueviews:searchrequest\n/secure/RunPortlet

#
# Default Timeout. The TrustedApplication sends an encrypted timestamp in the request. Do not allow if the timestamp is
# greater than the timeout (in milliseconds) ago.
#
jira.trustedapps.timeout.default=10000

#
# The UserNameTransformer class name. This is useful if the external clients return user-names in mixed case
# and the JIRA internal database is all lower-case by default. This setting should only be changed under instruction
# from Atlassian support.
#
# For further info please see JRA-14414
#
# This defaults to com.atlassian.jira.security.auth.trustedapps.UserNameTransformer.LowerCase if empty or missing
#
# Possible values:
# empty (LowerCase - default)
# com.atlassian.jira.security.auth.trustedapps.UserNameTransformer.LowerCase
# com.atlassian.jira.security.auth.trustedapps.UserNameTransformer.NoOp
#
# The NoOp version will simply pass through the supplied username in whatever case it retrieves it.
#
#jira.trustedapps.user.name.transformation.policy.class=

#--------------------------------------------------------------------------------------------

# JRA-15133: set this property to true if you create issues via email and don't want to save attached email messages
# to the created JIRA issue
#jira.option.ignore.email.message.attachments=false

#-----------------------------------------------------------------------------------------------------------------------
# Emulation of Internet Explorer MIME sniffing
#-----------------------------------------------------------------------------------------------------------------------
#
# JIRA accepts attachments from users and as such, when showing those attachments to other users, risks a form of
# security breach known as a Cross Site Scripting (XSS) attack. Hostile users (or their compromised accounts) who can
# upload an attachment could be able to acquire access to JIRA on behalf of another user (such as an administrator)
# with a specially crafted attachment. Internet Explorer ignores the Content-Type header sent by a server
# to indicate whether or not a file is text/html (and can contain a script) and will execute script code deviously
# embedded in other file types. The default behaviour as of JIRA 3.12 is to detect when IE would do this and in those
# cases force IE to download the file (or at least to prompt the user). Firefox and Safari users are unaffected by this
# since those browsers comply with the standard regarding Content-Type headers sent by the server.
#
# Three options for attachment downloading policy are available:
#
# secure
# workaround
# insecure
#
# workaround (default) is a reasonably safe option which forces Internet Explorer to download attachments that its
# "mime sniffing" would mistakenly detect it to be an html file. In addition, actual declared html attachments are
# never displayed inline for any browser.
#
# secure is a more paranoid mode which forces all attachments to be downloaded rather than displayed inline. This
# option is designed for high security requirements. Note that users who are prompted may still choose to let IE handle
# the file and may still be prey to an XSS attack.
#
# insecure is an open mode which allows all attachments to be shown inline. If a user decides to add javascript to an
# attachment, this will run in the context of the application and any user who views the attachment is at risk of the
# javascript code being run in their session on their behalf. Only use this option if you know what you are doing and
# have done your own research to determine that this does not undermine your security expectations.

jira.attachment.download.mime.sniffing.workaround=workaround