########################################################################################################################
#
# JIRA HOME
#
########################################################################################################################
#
# The jira.home property must be set before you start JIRA. It specifies the directory in which JIRA will store its data files.
#
# This must be set to an absolute path. Relative paths are not allowed.
#
# Ensure that only one JIRA instance uses the specified JIRA Home.
#
# NOTE: If you are using Windows, you will need to use double \ characters, for example c:\jira\home should be written
# as c:\\jira\\home
#
# You can also use Unix-like paths which Java/JIRA can handle, eg c:/jira/home
#
jira.home = 

########################################################################################################################
#
# JIRA SECURITY SETTINGS
#
########################################################################################################################

#-----------------------------------------------------------------------------------------------------------------------
#
# This property controls whether XSRF security token protection is enabled in JIRA
#
# (See http://en.wikipedia.org/wiki/Cross-site_request_forgery for more general information about this type of web attack vector.)
#
# This setting is ON by default in JIRA and is only shown here as an example.  We recommend that you NEVER set this to 'false'.
#
#jira.xsrf.enabled=true

#-----------------------------------------------------------------------------------------------------------------------
#
# This property controls whether to show the 'Remember my login on this computer' checkbox on login.
# Storing cookies is conceivably a security risk if users frequently share computers.
#
jira.option.allowcookies=true

#-----------------------------------------------------------------------------------------------------------------------
# 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

#-----------------------------------------------------------------------------------------------------------------------
# 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\n/rest\n/rpc/soap\n/plugins/servlet/streams\n/plugins/servlet/applinks

#
# 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=


########################################################################################################################
#
# JIRA LOOK AND FEEL
#
########################################################################################################################
#
# NOTE: Many of these properties can also be changed via the Administration interface.
# See the 'JIRA ADMINISTRATOR'S GUIDE' for details.
#
#-----------------------------------------------------------------------------------------------------------------------
# This property specifies an 'Announcement Banner' to display at the top of all pages. It can contain HTML tags.
#
# jira.alertheader =

# This property sets the visibility of the Announcement Banner.
# Values are: 'public' (show to anyone) or 'private' (show to logged-in users only)
#
jira.alertheader.visibility=private

#-----------------------------------------------------------------------------------------------------------------------
# This property specifies the name that will be displayed on the JIRA login page and the dashboard.
#
jira.title = JIRA

#-----------------------------------------------------------------------------------------------------------------------
# These properties control the global 'Logo' image which is displayed on every page in JIRA:
#
jira.lf.logo.url = /images/jira111x30.png
jira.lf.logo.width = 111
jira.lf.logo.height = 30

# This property applies to project logos ('Avatars').
# It specifies the maximum size of images that the Avatar Picker can handle,
# in MegaPixels (where one megapixel is one million pixels)
#
jira.avatar.megapixels=10

#
# JIRA displays error messages about unsupported browsers.
# If you want to suppress these warnings set the value to true
jira.browser.unsupported.warnings.disabled=false

#-----------------------------------------------------------------------------------------------------------------------
# This id is used to scope CSS selectors for javascript controls:
#
jira.lf.application.id = jira

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

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

# 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 = #114070

# 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
jira.lf.menu.separator = #f0f0f0

# These are the colors of hyperlinks in JIRA:
#
jira.lf.text.linkcolour = #3c78b5
jira.lf.text.activelinkcolour = #3c78b5

# This is the color of JIRA page headings:
#
jira.lf.text.headingcolour = #3c78b5

# These colors control the default values of the gadget chromes on the dashboard:
#
jira.lf.gadget.color1=#369
jira.lf.gadget.color2=#900925
jira.lf.gadget.color3=#d94625
jira.lf.gadget.color4=#346006
jira.lf.gadget.color5=#003366
jira.lf.gadget.color6=#411E66
jira.lf.gadget.color7=#bbb

#-----------------------------------------------------------------------------------------------------------------------
# Gadgets
#-----------------------------------------------------------------------------------------------------------------------
#
# This property limits the number of gadgets that may be added to a dashboard in JIRA.
# If this property is omitted, it will default to 20.
#
jira.dashboard.max.gadgets=20

# If this property is set to true, the 'Login' gadget will not be added to the dashboard for logged-out users.
# If you would like to force https only for the login screen but nowhere else in JIRA, set this property to true.
# See JRA-17727
#
jira.disable.login.gadget = false

# The default columns for the 'Voted' gadget
#
jira.table.cols.voted = issuetype, issuekey, summary, priority, status
#
# The default columns for the 'Watched' gadget
#
jira.table.cols.watched = issuetype, issuekey, summary, priority, status

# The maximum number of rows a user can display in a table gadget. A higher number my result in performance issues
#
jira.table.gadget.max.rows = 50

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


#-----------------------------------------------------------------------------------------------------------------------
# Charts
#-----------------------------------------------------------------------------------------------------------------------
#
# These properties specify the maximum number of 'Days Previous' for which a chart can be generated for a certain time period.
# Generally this should be limited such that you can only generate about 250 datapoints.  This means that the generated chart
# will have 1-2 pixel wide bars if the maxium data range is generated for a period.
#
# Please note that increasing these values can have a very large impact on performance, and will generally produce charts
# that don't show useful information.
#
# Valid periods as defined by com.atlassian.jira.charts.ChartFactory.PeriodName are:
# hourly, daily, weekly, monthly, quarterly, yearly
#
# If no mapping can be found, the default value of 1000 days will be used.
#
jira.chart.days.previous.limit.yearly=36500
jira.chart.days.previous.limit.quarterly=22500
jira.chart.days.previous.limit.monthly=7500
jira.chart.days.previous.limit.weekly=1750
jira.chart.days.previous.limit.daily=300
jira.chart.days.previous.limit.hourly=10

#-----------------------------------------------------------------------------------------------------------------------
# Project 'Summary' screen
#-----------------------------------------------------------------------------------------------------------------------
# The number of issues shown on the 'Summary' tab when browsing a project.
#
jira.project.summary.max.issues=3

#-----------------------------------------------------------------------------------------------------------------------
# Project Release Notes
#-----------------------------------------------------------------------------------------------------------------------
#
# These list the templates that can be used for generating Release Notes (ie. changelogs).
# For each template, there needs to a corresponding entry in *both* of the following properties:
#
jira.releasenotes.templatenames = Html, Text
jira.releasenotes.templates = releasenotes-html.vm, releasenotes-text.vm

# The default format for Release Notes:
#
jira.releasenotes.default = Html


#-----------------------------------------------------------------------------------------------------------------------
# 'View Issue' screen
#-----------------------------------------------------------------------------------------------------------------------
# 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

# Specifies the sort order of the issue links on the 'View Issue' screen.
# The value is a comma-separated list which can contain 'key', 'type', 'status', 'priority' or 'resolution'
#
jira.view.issue.links.sort.order = type, status, priority

# The width of field labels on the 'View Issue' screen.  This must be a number and is converted into 'm'-widths on the page.
#
#jira.lf.field.label.width=11

# Uncommenting the following property (and leaving it set to true) will prevent the 'Operations' bar on the 'View Issue' page
# from tracking down the page with the user.
#
#jira.disable.operations.bar=true

# This is the default group size for the 'Operations' bar (before adding a drop-down)
#
#ops.bar.group.size = 2

# This is the size of the 'Actions' group in the 'Operations' bar:
#
#ops.bar.group.size.opsbar-operations = 2

# This is the size of the 'Workflow' group in the 'Operations' bar:
#
#ops.bar.group.size.opsbar-transitions = 2

# The columns to show when viewing issues in a table (eg. the 'Linked Issues' section on the 'View Issue' page).
# The values that you can put here are valid values from IssueFieldConstants.
#
jira.table.cols.linkedissue = issuetype, issuekey, summary, status, priority


#-----------------------------------------------------------------------------------------------------------------------
# Subtasks
#-----------------------------------------------------------------------------------------------------------------------

# The columns to show when viewing sub-task issues in a table  (ie. the 'Sub-Tasks' section on the 'View Issue' page).
# 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 property controls whether to show the 'Subtask quick creation form' on the 'View Issue' page for issues that have no sub-tasks yet.
jira.view.issue.show.quicksubtask.when.no.subtasks=false

# This template formats the 'Subtask 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 'Subtask 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


#-----------------------------------------------------------------------------------------------------------------------
# Autocomplete
#-----------------------------------------------------------------------------------------------------------------------
# Specifies the number of results to display in the AJAX autocomplete pickers
jira.ajax.autocomplete.limit=20

# Specifies Whether or not the AJAX issue-picker is enabled
jira.ajax.autocomplete.issuepicker.enabled = true

# Specifies the maximum number of users that can be used with the AJAX user-picker
jira.ajax.autocomplete.userpicker.limit = 5000

# Specifies the maximum number of suggestions to show for labels. Setting this property to 0 will not impose a limit on
# suggestions at all.  This may be quite slow, however.
jira.ajax.autocomplete.labelsuggestion.limit = 20


#-----------------------------------------------------------------------------------------------------------------------
# Links
#-----------------------------------------------------------------------------------------------------------------------
# These two settings control whether Trackback is enabled in JIRA.
# (Trackback is a means of telling websites that a page has been linked to.)
# By default, JIRA will receive trackbacks but not send them.
#
jira.option.trackback.send = false
jira.option.trackback.receive = true

# The prefix added to the Summary field of cloned issues:
jira.clone.prefix = CLONE -
# The type of link to create between a cloned issue and the issue from which it was cloned:
jira.clone.linktype.name = Cloners

# A prefix for the custom field that links to the old issue for imported issues (eg from 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 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



########################################################################################################################
#
# USER SETTINGS
#
########################################################################################################################

# Specifies the default number of issues per Issue Navigator page. (Individual users can change this.)
user.issues.per.page=50

# Specifies whether to notify users about their own changes on watched issues. (Individual users can change this.)
user.notify.own.changes=true

# Specifies whether filters and dashboards are shared with everyone by default. (Individual users can change this.)
user.default.share.private=true

# Specifies the default value for notification mimetype preference (ie. html or text emails) in User Preferences:
user.notifications.mimetype=text

# Specifies whether to show 'Actions' and 'Operations' in the Issue Navigator
user.show.actions.in.navigator=true

# Whether the keyboard shortcuts are enabled or not
user.keyboard.shortcuts.disabled=false

# Specifies the maximum number of 'Issue History' records to keep for each user:
jira.max.Issue.history.items = 50

# Specifies the maximum number of issue entries to show in the 'Issue History' drop-down.  This is actually one more than shown.
jira.max.issue.history.dropdown.items = 6

# Specifies the maximum number of filter entries to show in the 'Issue Filter' drop-down.
jira.max.issue.filter.dropdown.items = 10

# Specifies the default maximum number of history records to keep for a user.
# This is used for items we tore history for but don't specify an explicit key for in the form - jira.max.<type>.history.items
jira.max.history.items = 10

# Specifies the default maximum number of JQL queries in the history.
jira.max.JQLQuery.history.items = 10

# Specifies the default maximum number of Admin Pages in the history.
jira.max.AdminPage.history.items = 5

# Controls whether JIRA will prompt users for logout confirmation.
# Valid values are 'never' (default), 'cookie' (ie. prompt only if the user was logged in via a cookie), 'always'.
jira.option.logoutconfirm = never

# If this option is set to false, users avatars will no longer be shown anywhere in the UI. This will also disable
# the user hover.
jira.user.avatar.enabled=true

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

# This setting applies to comment visibility. It determines whether the 'Viewable by' drop-down includes groups or only project roles.
# true = Both Groups and Project Roles are included
# false = Groups are not included
#
jira.comment.level.visibility.groups=false

# This setting applies to 'Scheme Tools', which are used for migrating users from groups to project roles.
# It determines 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


########################################################################################################################
#
# PROJECT KEY SETTINGS
#
########################################################################################################################
#
# 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]+)

# 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

# A space/comma separated list of reserved words that cannot be used as keywords.
# 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


########################################################################################################################
#
# ISSUE KEY SETTINGS
#
########################################################################################################################
#
# Specifies whether 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

# 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


########################################################################################################################
#
# TIME AND DATE SETTINGS
#
########################################################################################################################
#
jira.lf.date.time = h:mm a
jira.lf.date.day = EEEE h:mm a
#
# These are in Java format (see http://java.sun.com/j2se/1.4.2/docs/api/java/text/SimpleDateFormat.html).
# If you specify yyyy in the format for a SimpleDateFormatter then '08' becomes '0008'. If you specify yy then '08' becomes '2008'.
# Read the SimpleDateFormat documentation for more details before changing the year field.
#
jira.lf.date.complete = dd/MMM/yy h:mm a
jira.lf.date.dmy = dd/MMM/yy
#
# This property controls whether to display dates relative to now (eg.'Today, 2:12pm'):
jira.lf.date.relativize = true

#-----------------------------------------------------------------------------------------------------------------------
#
# These two properties need to match for the date-picker to perform correctly.
# The first date is in Java format (see http://java.sun.com/j2se/1.4.2/docs/api/java/text/SimpleDateFormat.html).
# The second is 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 JIRA administration interface.
#
# If you specify yyyy in the format for a SimpleDateFormatter then '08' becomes '0008'. If you specify yy then '08' becomes '2008'.
# Read the SimpleDateFormat documentation for more details before changing the year field.
#
jira.date.picker.java.format = d/MMM/yy
jira.date.picker.javascript.format = %e/%b/%y

#-----------------------------------------------------------------------------------------------------------------------
#
# These two properties need to match for the date-time-picker to perform correctly.
# The first date is in Java format (see 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.
#
# If you specify yyyy in the format for a SimpleDateFormatter then '08' becomes '0008'. If you specify yy then '08' becomes '2008'.
# Read the SimpleDateFormat documentation for more details before changing the year field.
#
jira.date.time.picker.java.format = dd/MMM/yy h:mm a
jira.date.time.picker.javascript.format = %e/%b/%y %I:%M %p

# This property controls whether ISO8601 standard is used to render calendar days/weeks
# (see http://en.wikipedia.org/wiki/ISO_8601 for more details)
#
jira.date.time.picker.use.iso8061 = false


########################################################################################################################
#
# TIME TRACKING
#
########################################################################################################################
#
# These properties define your organization's number of working hours per day and working days per week.
# You can use a decimal point if you wish.
#
jira.timetracking.hours.per.day=8
jira.timetracking.days.per.week=5

#
# Valid values for format are 'pretty', 'hours', 'days':
#
jira.timetracking.format=pretty

#
# Since JIRA 4.2, Logging Work can now be done on transitions by adding the Log Work field to the transition's screen.
# However, only one input for the comment of the transition and the work description is displayed.
# If this flag is set to true, the value of that input will be used for both the transition comment (and security level)
# and the work description (and worklog security level).
# If this flag is set to false, the value of the input will only be used for the transition comment (and security level);
# the work description will contain no comment and will be visible to all.
#
jira.timetracking.copy.comment.to.work.desc.on.transition=true

#-----------------------------------------------------------------------------------------------------------------------
#
# Prior to JIRA 4.2, the 'Original Estimate' and 'Remaining Estimate' could not be edited independently and
# would synchronize values when work had not been logged.
#
# Since 4.2 the values can be independently edited and are not tied to each other in any way.
#
# This property allows you to change back to the legacy behavior:
#
jira.timetracking.estimates.legacy.behaviour=true

########################################################################################################################
#
# ATTACHMENTS
#
########################################################################################################################
#
# Specifies whether to show thumbnails of images attached to issues (default is 'true').
#
jira.option.allowthumbnails=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

#
# Defines the number of zip entries to show on the view issue screen
#
jira.attachment.number.of.zip.entries=30

# JIRA can interpret ZIP files and also download all attachments as ZIP files.  This may be expensive
# when it involves very large attachments or large files that do not compress well.
#
jira.attachment.allow.zip.support=true

# If you would like to disable the 'Screenshot' applet, set this property to false:
#
jira.screenshotapplet.enabled=true

# If you would like to enable the screenshot applet for linux set this property to true.  Linux sceenshot support is known to be flakey.
#
jira.screenshotapplet.linux.enabled=false

#
# Defines a comma-separated list of the file extensions that JIRA won't expand as a ZIP in the view issue screen.
# By default, it includes the MS Office OpenXml extensions and OpenOffice OpenDocument extensions.
#
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


########################################################################################################################
#
# EMAIL SETTINGS
#
########################################################################################################################
#
# 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)

#-----------------------------------------------------------------------------------------------------------------------
# Specifies 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

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

#-----------------------------------------------------------------------------------------------------------------------
# JIRA will send notification emails to both the previous assignee and the current assignee, whenever the 'Assignee' field changes.
#
# However, past versions of JIRA only sent a notification email to the previous assignee IF the operation that changed the event
# was the 'Assign Issue' operation.  It did not send a notification if the issue was edited in some other way.
#
# This property allows the old behaviour to be re-instated, for those customers who liked the old behaviour.
#
# See http://jira.atlassian.com/browse/JRA-6344 for more details
#
jira.assignee.change.is.sent.to.both.parties=true

#-----------------------------------------------------------------------------------------------------------------------
# Specifies the number of recipients to send to in each email when using the 'Send Bulk Email' function in JIRA.
#
jira.sendmail.recipient.batch.size=100

#-----------------------------------------------------------------------------------------------------------------------
# Specifies how user email addresses are displayed on the 'Profile' page. The options are:
# 'show' - email addresses are visible to all users.
# 'mask' - email addresses are masked (e.g. 'user@example.com' is displayed as 'user at example dot com').
# 'hide' - email addresses are hidden from all users.
# 'logged-in' - only users logged in to JIRA can view the email addresses.
#
jira.option.emailvisible = show

#-----------------------------------------------------------------------------------------------------------------------
# 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 (see JRA-15133).
#
#jira.option.ignore.email.message.attachments=false


########################################################################################################################
#
# IMPORT/EXPORT SETTINGS
#
########################################################################################################################

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

# Thie property specifies whether  whether automatic export (backup) of your JIRA issue data occurs on upgrade.
jira.autoexport=true


########################################################################################################################
#
# SEARCHING
#
########################################################################################################################
#
# The maximum number of results the 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

# 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 must be EQUAL TO OR GREATER 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 =

#-----------------------------------------------------------------------------------------------------------------------
# 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, but 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

#-----------------------------------------------------------------------------------------------------------------------
#
# The maximum clause limit in Lucene.
# Set this to higher than your expected number of issues, to ensure that date-range searches across all issues will 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 following line:
# jira.i18n.default.locale = en_US

# The following property specifies 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

#-----------------------------------------------------------------------------------------------------------------------
#
# This property specifies whether JIRA should embed i18n key meta-data when rendering pages.
jira.i18n.include.meta-data=true

# 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

# 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 = 1000


#-----------------------------------------------------------------------------------------------------------------------
# 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

# Interactive mode:
jira.index.interactive.mergefactor = 4
jira.index.interactive.maxmergedocs = 2147483647
jira.index.interactive.maxbuffereddocs = 300

#-----------------------------------------------------------------------------------------------------------------------
# Websudo settings - Temporary Administrative Access
#-----------------------------------------------------------------------------------------------------------------------

# Is websudo disabled
jira.websudo.is.disabled = false
# How long will a websudo session last in minutes
jira.websudo.timeout = 10


########################################################################################################################
#
# TROUBLESHOOTING
#
########################################################################################################################

# 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

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

# A counter that can be used to flush superbatched web-resources
#
jira.webresource.superbatch.flushcounter=1


########################################################################################################################
#
# NOTES FOR DEVELOPERS
#
########################################################################################################################
#
# 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
#
# The keys must match up with the keys found in APKeys.java
