Parameter

Accepts

Default Value

Since Version

Usage Notes

deskzilla.license/jiraclient.license

A valid file path (either absolute or relative to Deskzilla installation directory)

1.2

Sets the license key to be used. If not set, the user may be asked for a license key. If set to an invalid or non-existing file, Deskzilla will not be able to start.

deskzilla.workspace/jiraclient.workspace

A valid directory path

.Deskzilla subdirectory in the user's home dir

1.2

Sets the workspace to be used. Alternatively, the workspace directory may be specified as a parameter, e.g. deskzilla.exe C:/path/to/workspace.

deskzilla.home/jiraclient.home

Valid existing directory name

1.0

Sets the home directory for Deskzilla. If not set, the directory is guessed based on the current directory and the directory where Deskzilla executables are located.

deskzilla.debug/jiraclient.debug

True/false

1.0

If set to true, Deskzilla will give more detailed output to the console and to log files.

no.splash

True/false

1.0

If true, Deskzilla will not show a splash screen when starting.

show.unsync.counters

True/false

1.1

If true, unsynchronized queries will also show the number of bugs (in the database).

debug.counters

True/false

1.1

If true, Deskzilla will log statistics about queries counting.

no.winlaf

True/false

1.0

If true, do not patch Windows look and feel with winlaf project.

use.metal

True/false

1.0

If true, use metal look-and-feel.

socket.timeout

Positive integer number (milliseconds)

30000

1.0.2

Defines the SO_TIMEOUT parameter for all sockets in the application. If there's no response from server for the specified amount of milliseconds (not seconds!), the connection will abort.

force.http10

True/false

1.1

Makes Deskzilla connect to HTTP servers using HTTP/1.0 regardless of server capabilities.

force.http11

True/false

1.1

Force HTTP/1.1. Not used.

bugzilla.dump

All/errors

1.0.2

Makes Deskzilla log pages that are returned from Bugzilla into "bugzilla" folder under "log" folder. If set to "errors", only pages that caused exceptions or errors will be logged.

disable.new.version.check

True/false

1.1

If true, no automatic checks for a new version of the application will be made.

font.size

Integer

1.1

Changes default font size for the application. The number corresponds to the font size of a label. If default font size of some component is different from the default size of a label, then the size will be scaled.

font.size.abs

Integer

1.1

Changes default font size for the application. Sets the specified number as the default font size for all components.

auto.sync.period

Integer

30

1.1

Obsolete as of: Deskzilla 1.6, JIRA Client 1.3. Use full.sync.period and quick.sync.period. Sets the number of minutes between automatic resynchronization.

auto.sync.period.failed

Integer

10

1.1 Obsolete as of: Deskzilla 1.6, JIRA Client 1.3. Use full.sync.period.failed

Sets the number of minutes between automatic resynchronization.

arial.unicode

True/false

Unspecified

1.1.1

If set to true, forces Deskzilla to use font "Arial Unicode MS" instead of Tahoma. This may be needed to make Deskzilla display Chinese characters correctly.

form.combobox.drop.count

OS-specific

Positive integer

1.2.1

If set, overrides the default value for the maximum number of options appearing in the drop-down box of certain comboboxes (Component, Version, Milestone, etc).

debug.httpclient

True/false

False

Deskzilla 1.3

If set, allows all httpclient log messages into the application log.

bugzilla.xml.maxload

Positive integer

100

Deskzilla 1.5.1

Sets the maximum number of bugs requested from Bugzilla's xml.cgi with a single HTTP request. When Deskzilla needs to download more bugs, it will break download into several requests.

jira.xml.maxload

Positive integer, 10 <= maxload <= 1000

100

JIRA Client 1.3

Obsolete as of JIRAClient 3.5

Sets the default page size for loading issues in XML form from issue navigator.

Even if you set maxload to some value, JIRA Client in certain cases may ask for larger pages to perform correct download.

jira.reload.stepback

Positive integer (milliseconds)

64800000 (18 hours)

JIRA Client 1.3

Sets the amount of time JIRA Client steps back from synchronization point when loading changed issues.

full.sync.period

Positive integer (minutes)

720 (12 hours)

Deskzilla 1.6, JIRA Client 1.3

Sets the period of full synchronization, which loads all metadata from the server and may take some time.

full.sync.period.failed

Positive integer (minutes)

=full.sync.period

Deskzilla 1.6, JIRA Client 1.3

Sets the period between failed full sync and next full sync attempt.

quick.sync.period

Positive integer (seconds)

150 (2.5 minutes)

Deskzilla 1.6, JIRA Client 1.3

Sets the period between quick synchronizations.

jira.loadmeta.pt.max

Positive integer

100

JIRA Client 1.3

If the PROJECTS*TYPES number is greater than this setting, JIRA Client will not load custom fields per-project, per-issuetype. If you have large number of projects and your custom fields are highly configured (enabled for specific projects AND issue types), you might need to increase this number.

no.spellcheck

"true"

JIRA Client 1.3, Deskzilla 1.6; not effective in JIRA Client 1.7

Use this option to disable spell checker.

spellcheck

"true"

JIRA Client 1.7
Obsolete as of JIRA Client 3.6

Use this option to enable spell checker.

dz.ignore.product.defaults

"true"

Deskzilla 1.6 hf 15

Starting with version 1.6, Deskzilla sets all values on the New Bug form to the product defaults, as seen on the "New Bug" Bugzilla web page. Use this option to make Deskzilla behave like in older versions: remember the last used values for fields per project.

bugzilla.qload.noattach

"true"

Deskzilla 1.6

When set, Deskzilla will ask Bugzilla not to send attachments with xml bug info. This option may be used as a workaround to out-of-memory caused by a large attachment in XML.

bugzilla.xml.req.mindelay

Integer from 0 to 60

0

Deskzilla 1.7

When set to non-zero, defines the number of seconds that must pass between consecutive page load during long query download.

action.customcopy.pattern

Text

JIRAClient 3.2

Pattern of custom copy action

action.customcopy.name

Text

JRIAClient 3.2

Name of custom copy action

auto.download.maxsize

Positive integer (bytes)

102400

Maximum size of an attachment that JIRAClient downloads without explicit user's action. Default is 100Kb.

jiraclient.jql.maxresult

Positive integer

100

JIRAClient 3.2

Maximum number of issue that user is allowed to query via REST API

newIssue.allowMultipletrue/falsefalse

JIRAClient 3.6 hf 136
build 9204.136 and later

If set to false (default) only one New Issue window is allowed per connection. Next invocation of "New Issue" action focuses previously open window.
If set to true - you may open several New Issue windows. Next invocation of "New Issue" action opens one more New Issue window.

Affected actions: New Issue, New Issue Here, New Sub-Task.

assignee.filtertrue/falsetrueJIRAClient 3.6 hf 136
build 9204.136 and later

If set to true (default) Assignee editor shows only assignable users.
If set to false - Assignee editor shows all known users including not assignable.

Use the option if you have many assignable users on your server and the list of assignable users is cut off at some position (generally only first 50 assignable users are available).

upload.finalstatemodetrue/falsefalseJIRAClient 3.1.3Controls how to upload successive changes. Read more about how JIRA Client uploads Move issue and work flow steps.
workflow.resolve.defaultResolutionTextJIRAClient 3.6 hf 138
Build 9204.138 and later

Name of default resolution. This option used to choose default value for Resolution field.
If no value is specified JIRAClient searches for resolution named "Fixed" ("Fixed" translated to supported languages).
If the value is specified JIRAClient selects resolution with specified name (case is ignored).

Example: If desired default resolution name is "Shipped" set workflow.resolve.defaultResolution=shipped.

jiraclient.comment.htmltrue/falsefalseJIRAClient 3.6.2 hf 168
Build 9204.168 and later 
If set to true JIRAClient removes HTML tags from comment text. The default false value means that JIRAClient shows comment texts as is (as they are downloaded from server).
This option may be helpful when JEditor plugin is installed on server. JEditor plugin inserts HTML tags into the comments, this makes comments hard to read.
This option may slow down issue loading into issue table.
Note: This optional does not render HTML, it just removes HTML tags from text - this makes texts easier to read.
alm.format.timeDate/Time format pattern-JIRAClient 3.7 hf 32If specified used to display and parse time.
Examples:
HH:mm - 24-hours (0-23) (00:01, 23:59)
hh:mm a - 12-hours (1-12), AM/PM (12:01 AM, 11:59 PM)
Full list of supported pattern letters: https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html
alm.format.dateDate/Time format pattern-JIRAClient 3.7 hf 32

If specified used to display and parse date.
Examples:
yyyy/MM/dd - 4-digits year, 2-digits (leading zero) month, 2-digits (leading zero) day (2016/02/10)
yyyy/MMM/dd - 4-digits year, 3-letters month, 2-digits (leading zero) day (2016/Feb/10)
Full list of supported pattern letters: https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html

Attention: Check your date queries after changing date format. If your queries contains absolute date constraints - this constrains may become invalid or even wrong (if you swap day and month).

jira.sprint.removeClosedtrue/falsetrueJIRAClient 3.8.1 hf 38

If set to false, JC does not remove closed Sprints on Reload JIRA Configuration. The consequences are:

  1. Closed Sprint are not removed. Distribution by Sprint does not disappear (when no Open Sprint)
  2. JC will keep Sprints forever, there is no way to remove a Sprint from JC's cache.