|
Parameter |
Short |
Value |
Multiple Use Allowed |
Description |
---|---|---|---|---|---|
1 |
a |
|
|
Requested operation to perform. Valid actions are listed at the end. |
|
2 |
|
|
|
SQL to run after a successful action. Limited to specific actions at this time. |
|
3 |
|
|
|
Append values to existing values for version fields, components field, and custom fields supporting multiple values. For some actions using the file parameter, append will append output to the existing file. |
|
4 |
|
|
|
For run actions, this option will automatically clear an existing file on the first append requested. |
|
5 |
|
|
|
Column selection and ordering when action generates CSV output. A comma separated list of column numbers (1-based) or column names (case insensitive). Only columns provided by the selected outputFormat are available for selection. Invalid columns will be ignored. |
|
6 |
|
|
|
Comment text. |
|
7 |
|
|
|
Common parameter string added to all run actions. |
|
8 |
|
|
|
Comma separated list of component names or ids. |
|
9 |
|
|
|
Allow overriding environment settings for connect and read timeouts on URL connections. In milliseconds, 0 means infinite. |
|
10 |
|
|
|
Continue processing even after errors are encountered for run actions. Also used for some action to ignore certain errors like not found errors on remove actions. |
|
11 |
|
|
|
Name of file to restore and persist cookies across invocations of CLI actions. Can be used to provide Data Center session affinity for actions using REST APIs. |
|
12 |
|
|
|
A customer identified by an email address and name. Usually means a portal only user, but, in some cases, may also include full users. |
|
13 |
|
|
|
Database name is required for SQL actions. |
|
14 |
|
|
|
Format string for dates in Java SimpleDateFormat. Default for output is client date format. Default for date parsing is lenient starting with client date format and then some other standard formats based on JSON date format. |
|
15 |
|
|
|
Alternate format string for dates in Java SimpleDateFormat. Use specific (may be ignored), but normally used for date only fields to avoid longer dateFormat based output. Some uses default to yyyy-MM-dd. |
|
16 |
|
|
|
Database table needs to be created before adding rows. |
|
17 |
|
|
|
By default, lib/jdbc is used to automatically load database drivers. Otherwise you can specify a specific file or url reference for the database driver jar. Example /jdbcDrivers/postgresql-42.1.4.jar or https://jdbc.postgresql.org/download/postgresql-42.1.4.jar
|
|
18 |
|
|
|
Database user password. Defaults to password. |
|
19 |
|
|
|
Database table name when creating or updating a database from list output. |
|
20 |
|
|
|
Comma separated list of column names used to access existing rows for update. Normally this defines a primary key set for the table. |
|
21 |
|
|
|
Database user name. Defaults to user. |
|
22 |
|
|
|
Requests detail debug output. Optional for all actions. |
|
23 |
|
|
|
Description of a request. |
|
24 |
|
|
|
JDBC driver class or predefined value: postgresql, mysql, mssql, oracle, or db2400. Required for SQL actions. |
|
25 |
|
|
|
Character encoding (character set) for text based file content - must be an encoding supported by your JAVA platform. |
|
26 |
|
|
|
Use to set client and construct specific fields or variables using name=value syntax. The first equal sign (=) delineates the name from it's value. This provides a more convenient and expandable alternative for setting field or variables and is the recommended approach. Values are trimmed unless single quoted and single quoted strings will have single quotes removed. This provides a more convenient and expandable way to set fields as an alternative to the fields and numbered field parameters. |
|
27 |
|
|
|
Deprecated. Field name. Value is specified by the value1 parameter. |
|
28 |
|
|
|
Deprecated. Field name. Value is specified by the value2 parameter. |
|
29 |
|
|
|
Deprecated. Use the multiple field parameters. Use to specify request fields. A comma separated list of key:value pairs. Single quote the key:value pair if it contains a comma (,) or line breaks. An alternative is to use a JSON formatted string to represent the list of key:value pairs. |
|
30 |
f |
|
|
Path to file based content or result output. Use - for standard input. Use + for getting lines from 'input' parameters. |
|
31 |
|
|
|
Successively find and replace matching text with the find and replace values specified using find:replace syntax. The first colon ( delineates the find value from the replace value. Single quote values containing a color and then escape embedded quotes. Deprecated use is a comma separated list of the same. Recommend using multiple parameters instead. The deprecated use case is only valid when the multiple parameter feature is not being used. |
|
32 |
|
|
|
Successively find and replace matching text with the find and replace values specified using find:replace syntax. The first colon ( delineates the find value from the replace value. Single quote values containing a color and then escape embedded quotes. The find value must be a valid regular regular expression and the replace value can contain replacement variables for capture groups like $1, $2, and so on. For some command shells, the $ may need to be escaped. Deprecated use is a comma separated list of the same. Recommend using multiple parameters instead. The deprecated use case is only valid when the multiple parameter feature is not being used. |
|
33 |
|
|
|
Request is made on behalf of another user. |
|
34 |
|
|
|
Prints this help message. |
|
35 |
|
|
|
Help text. |
|
36 |
|
|
|
Database host server for SQL actions. Not used if url is provided. Defaults to localhost if not provided. |
|
37 |
i |
|
|
Line of input used in place of file data for run actions. One or more input parameters are used as lines instead of using the file parameter. In some cases requiring a file parameter, it may be necessary to use a special value of + to indicate to use the input parameters instead. |
|
38 |
|
|
|
Jira issue type id. |
|
39 |
|
|
|
Maximum number of list entries to return. Some actions or environments may impose a more smaller default limit. |
|
40 |
|
|
|
Comma separated list of entries to populate the entry replacement variable on runFromList. Single quote values containing a delimiter. Embedded quotes must be doubled. |
|
41 |
|
|
|
Comma separated list of entries to populate the entry2 replacement variable on runFromList. Single quote values containing a delimiter. Embedded quotes must be doubled. |
|
42 |
|
|
|
Name. |
|
43 |
|
|
|
Comma separated list of support, experimental, or other client or action specific options. |
|
44 |
|
|
|
Organization name or id representing a grouping of users primarily for access permissions. |
|
45 |
|
|
|
Specify output format for a list actions. Output format determines what columns are retrieved for the list. More columns usually take longer to retrieve. |
|
46 |
|
|
|
CSV output from get list actions and pretty print output from get actions can optionally be converted to plain text, HTML, or json based on the value of this parameter. Get actions also support the variables output type to set replacement variables for use in a CLI run script. Valid values are: text, table, html, json, variables. |
|
47 |
|
|
|
A comma separated list of user ids for request participation or as organization members. |
|
48 |
p |
|
|
User password for remote access. Cloud users need to use an API token for almost all cases and the preference is to provide the token with the token parameter. However, for compatibility reasons, we still allow the token to be provided using the password parameter." |
|
49 |
|
|
|
Database host port for SQL actions. Optional, defaults to database default. Not used if url is provided. |
|
50 |
|
|
|
Request priority - name or id. |
|
51 |
|
|
|
Service desk project name, key, or id. Also known as a service desk. |
|
52 |
|
|
|
Property file with database parameters, field mappings, or client specific information. |
|
53 |
|
|
|
Limit some output messages. Optional for all actions. |
|
54 |
|
|
|
Reference to a replacement key value used to remember an action specific value like issue key, entity id, or similar so it can be referenced later. Each action that allows this parameter will specify that the reference parameter is valid for the action. |
|
55 |
|
|
|
Regular expression for condition matching or list filtering. |
|
56 |
|
|
|
Replace existing entity on add, create, or similar actions. |
|
57 |
|
|
|
Request key or id. |
|
58 |
s |
|
|
Server URL. Normally the same URL used when using a browser to access the server. This is a required parameter for most actions. |
|
59 |
|
|
|
Simulate running actions. Log the action that would be taken. |
|
60 |
|
|
|
Ordered list of alternate characters for comma ( , ), colon ( : ), at ( @ ), quote ( ' ), and double quote ( " ) characters used for specialized processing of some specific parameters. |
|
61 |
|
|
|
SQL select statement used to generate a run script. |
|
62 |
|
|
|
Summary of a request. |
|
63 |
t |
|
|
Cloud API token associated to your Atlassian account. Login to https://id.atlassian.comand go to Security - API tokens to create a token. |
|
64 |
|
|
|
Request type name or id. |
|
65 |
|
|
|
Action specific setting. Example: Database access url for SQL actions. Optional when host is provided. |
|
66 |
u |
|
|
User name for remote access. Cloud users are identified by email address. |
|
67 |
|
|
|
Field value or condition value for matching. |
|
68 |
|
|
|
Deprecated. Value corresponding to the field1 parameter name. |
|
69 |
|
|
|
Deprecated. Value corresponding to the field2 parameter name. |
|
70 |
|
|
|
Requests verbose output to help with problem determination. Optional for all actions. |