Usage:
  jira (-a|--action) <action> [(-f|--file) <file>] [--encoding <encoding>] [--debug] [-v|--verbose] [--quiet] [--outputFormat
  <outputFormat>] [--columns <columns>] [--connectionTimeout <connectionTimeout>] [--sql <sql>] [--driver <driver>] [--url <url>]
  [--host <host>] [--port <port>] [--database <database>] [--dbUser <dbUser>] [--dbPassword <dbPassword>] [--dbJar <dbJar>]
  [--dbTableafterSql <afterSql>] [--dbTable <dbTable>] [--dbTableKeys <dbTableKeys>] [--dbCreateTable] [--comment <comment>] [--replace]
  [--propertyFile <propertyFile>] [--common <common>]
  [--special <special>] [--dateFormat <dateFormat>] [--dateFormat2 <dateFormat2>]
  [--reference <reference>] [--findReplace <findReplace>] [--findReplaceRegex   <findReplaceRegex>] [--list <list>] [--list2 <list2>]
  [--options <options>] [--continue] [--simulate] [--append] [--clearFileBeforeAppend] (-s|--server) <server>   (-u|--user) <user>
  (-p|--password) <password> [--serviceapi <service><api>] [--cookiesservice <cookies><service>] [-l|--loginFromStandardInputcookies <cookies>] [--project
  <project>] [--toProject <toProject>]
  [--name <name>] [--description <description>] [--lead <lead>] [--defaultAssignee   <defaultAssignee>] [--after <after>] [--board
  <board>] [--issue <issue>] [--toIssue <toIssue>] [--parent <parent>] [--summary   <summary>] [--priority <priority>] [--reporter
  <reporter>] [--assignee <assignee>] [--security <security>] [--environment
  <environment>] [--component <component>] [--toComponent
  <toComponent>] [--components <components>] [--version <version>]   [--affectsVersions <affectsVersions>] [--fixVersions <fixVersions>]
  [--custom <custom>] [--field <field>] [--field2 <field2>]
  [--fieldExcludes <fieldExcludes>] [--date <date>] [--startDate
  <startDate>] [--issueType <issueType>] [--type <type>] [--resolution <resolution>] [--labels   <labels>] [--workflow <workflow>]
  [--transition <transition>] [--step <step>] [--screen <screen>] [--comment <comment>] [--filter   <filter>] [--jql <jql>] [--search <search>] [--regex
  <regex>] [--regex2 <regex2>] [--reference <reference>] [--link <link>]
  [--reverseLink <reverseLink>] [--value <value>] [--values <values>] [--values2
  <values2>] [--timeSpent <timeSpent>] [--estimate   <estimate>] [--originalEstimate <originalEstimate>] [--id <id>] [--propertyPrefix
  <propertyPrefix>] [--jsp <jsp>] [--request
  request <request>] [--requestParameters <requestParameters>] [--requestType <requestType>] [--acceptType
  <acceptType>] [--limit <limit>]
  [--api <api>] [--role <role>] [--group <group>] [--defaultGroup <defaultGroup>] [--userId <userId>] [--newUserId
  <newUserId>]
  [--userKey <userKey>] [--userFullName <userFullName>] [--userEmail <userEmail>] [--userPassword <userPassword>]
  [--autoGroup]   [--permissionScheme <permissionScheme>] [--notificationScheme <notificationScheme>] [--issueSecurityScheme
  <issueSecurityScheme>]   [--workflowScheme <workflowScheme>] [--issueTypeScheme <issueTypeScheme>] [--issueTypeScreenScheme
  <issueTypeScreenScheme>]
  [--fieldConfigurationScheme <fieldConfigurationScheme>] [--category <category>] [--template <template>]
  [--exportType <exportType>]   [--login <login>] [-l|--loginFromStandardInput] [--functionKey <functionKey>] [--targetServer
  <targetServer>] [--targetUser <targetUser>] [--targetPassword
  <targetPassword>] [--autoVersion] [--autoComponent] [--autoAdjust]
  [--asVersion] [--asComponent] [--asCascadeSelect] [--appendText]   [--subtract] [--suppressId] [--withId] [--exportAttachments]
  [--copyLinks] [--copyAttachments] [--copyComments] [--copyWatchers]
  [--copySubtasks] [--copySubtaskEstimates] [--useParentVersions]
  [--cloneIssues] [--copyVersions] [--copyComponents]   [--copyRoleActors] [--activate] [--deactivate] [--notify] [--suppressNotify]
  [--includeInactive] [--deleteFilter] [--favorite]
  [--lookup] [--legacy] [--preserveCase] [--recursive] [--helpText <helpText>]
  [--participants <participants>] [--organization <organization>] [--forUser <forUser>] [--help]


	Provides capability to make requests to a remote server.
	Required parameters: action, server, password.
	Optional parameters: user (likely required for your installation).
	Other required and optional parameters depending on action requested.


  (-a|--action) <action>
        Requested operation to perform. Valid actions are listed at the end.

  [(-f|--file) <file>]
        Path to file based content or result output. Use - for standard input.

  [--encoding <encoding>]
        Character encoding (character set) for text based file content - must be an encoding supported by your JAVA platform.

  [--debug]
        Requests detail debug output. Optional for all actions.

  [-v|--verbose]
        Requests verbose output to help with problem determination. Optional for all actions.

  [--quiet]
        Limit some output messages. Optional for all actions.

  [--outputFormat <outputFormat>]
        Specify output format for an action. (default: 1)

  [--columns <columns>]
        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.

  [--connectionTimeout <connectionTimeout>]
        Allow overriding environment settings for connect and read timeouts on URL connections. In milliseconds, 0 means infinite.

  [--sql <sql>]
        SQL select statement used to generate a run script.

  [--driver <driver>]
        JDBC driver class or predefined value: postgresql, mysql, mssql, oracle, or db2400. Required for SQL actions.

  [--url <url>]
        Action specific setting. Example: Database access url for SQL actions. Optional when host is provided.

  [--host <host>]
        Database host server for SQL actions. Not used if url is provided. Defaults to localhost if not provided.

  [--port <port>]
        Database host port for SQL actions. Optional, defaults to database default. Not used if url is provided.

  [--database <database>]
        Database name is required for SQL actions.

  [--dbUser <dbUser>]
        Database user name. Defaults to user.

  [--dbPassword <dbPassword>]
        Database user password. Defaults to password.

  [--dbJar <dbJar>]
        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-9.3-1102.jdbc41.jar or
        https://jdbc.postgresql.org/download/postgresql-9.3-1102.jdbc41.jar

  [--dbTableafterSql <dbTable><afterSql>]
        Experimental.SQL Databaseto tablerun nameafter whena creatingsuccessful oraction. updatingLimited ato databasespecific fromactions listat output.
this time.

  [--dbTable <dbTable>]
        Database table name when creating or updating a database from list output.

  [--dbTableKeys <dbTableKeys>]
        Experimental. Comma separated list of column names used to access existing rows for update. Normally this defines a primary key set for
     key set for the table.

  [--dbCreateTable]
        Experimental. Database table needs to be created before adding rows.

  [--comment <comment>]
        Comment text.

  [--replace]
        Replace existing entity on add, create, or similar actions.

  [--propertyFile <propertyFile>]
        Property file with mapping database parameters, field mappings, or client specific information.

  [--common <common>]
        Common parameter string added to all run actions.

  [--special <special>]
        Ordered list of alternate characters for comma ( , ), colon ( : ), at ( @ ), quote ( ' ), and double quote ( " ) characters
        used for specialized processing of some specific parameters.

  [--dateFormat <dateFormat>]
        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.

  [--dateFormat2 <dateFormat2>]
        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.

  [--findReplacereference <findReplace><reference>]
        FindReference andto replacea text.replacement Commakey separatedvalue listused ofto colonremember separatedan pairs.action Singlespecific quotevalue valueslike containingissue akey delimiter.or Embeddedsimilar so it can be
        referenced later.Each action that allows this parameter will specify what value is being set for the reference replacement
   quotes   must be escapedkey.

  [--findReplaceRegexfindReplace <findReplaceRegex><findReplace>]
        Find and replace text with a regular expression. Comma separated list of colon separated pairs. Single quote values containing a delimiter. Embedded
    containing a delimiter. Embedded quotes must be escaped.

  [--listfindReplaceRegex <list><findReplaceRegex>]
        Find and replace text with a regular expression. Comma separated list of colon separated entriespairs. Single quote values
        containing a delimiter. Embedded quotes must be doubled.

  [--continuelist <list>]
        ContinueComma processingseparated evenlist afterof errorsentries areto encounteredpopulate forthe runentry actions.replacement Alsovariable usedon forrunFromList. someSingle actionquote tovalues ignorecontaining certaina
errors        delimiter. likeEmbedded notquotes foundmust errors on remove actionsbe doubled.

  [--simulatelist2 <list2>]
        SimulateComma runningseparated actions.list Logof theentries actionto thatpopulate wouldthe beentry2 taken.replacement variable on  [--append]
   runFromList. Single quote values containing a
    Append values to existing valuesdelimiter. forEmbedded versionquotes fields,must componentsbe field,doubled.
and
custom fields supporting multiple values. For[--options <options>]
        Comma separated somelist actionsof using the file parametersupport, experimental, appendor willother appendclient outputor toaction thespecific existing fileoptions.

  [--clearFileBeforeAppendcontinue]
        ForContinue runprocessing actions,even thisafter option will automatically clear an existing file on the first append requested.

  (-s|--server) <server>errors are encountered for run actions. Also used for some action to ignore certain errors
        like not found errors on Serverremove URL. Normally the base URL of the server and the same as how the server is accessed from a browseractions.

  [--simulate]
        Simulate running actions. Log the action that would be taken.

  (-u|[--user)append]
<user>        Append Uservalues nameto forexisting remotevalues access. (default: automation)

  (-p|--password) <password>
   for version fields, components field, and custom fields supporting multiple values. For
    User password for remote access.some actions using the file parameter, append will append output to the existing file.

  [--service <service>clearFileBeforeAppend]
        ServiceFor addressrun extension. (default: /rpc/soap/jirasoapservice-v2)

  [--cookies <cookies>]
        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.

  [-l|--loginFromStandardInput]
actions, this option will automatically clear an existing file on the first append requested.

  (-s|--server) <server>
        Server URL. Normally the base URL of the server and the same as how the server is accessed from a browser.

  (-u|--user) <user>
       Get loginUser tokenname fromfor standardremote inputaccess. Only works for actions based solely on SOAP based server requests. Actions using REST(default: automation)

  (-p|--password) <password>
        User password for based server requests require passwords on each actionremote access.

  [--projectapi <project><api>]
        Project name, key, or idAPI version. Some requests produce [--toProject <toProject>]
        Project name, key, or id to copy to. For cloning issues, either toProject or project can be used.different results based on the api version used. (default: latest)

  [--service <service>]
        Service address extension. (default: /rest/api)

  [--namecookies <name><cookies>]
        Name. of file  [--description <description>]
        Description.

  [--lead <lead>]to restore and persist cookies across invocations of CLI actions. Can be used to provide Data Center session
        affinity for Projectactions leadusing userREST idAPIs.

  [--defaultAssigneeproject <defaultAssignee><project>]
        Project orname, compnentkey, defaultor assigneeid.
for
issues. For projects, default is unassigned with options: PROJECT_LEAD or [--toProject <toProject>]
        Project name, key, or id to UNASSIGNEDcopy (blank)to. For cloning componentsissues, default is PROJECT_DEFAULT with options: PROJECT_LEAD, PROJECT_DEFAULT, COMPONENT_LEAD
 either toProject or project can be used.

  [--name <name>]
      or UNASSIGNED (blank)Name.

  [--afterdescription <after><description>]
        VersionDescription.
name
or id to add a version after. Defaults to after last version. Use -1 to make it the first version[--lead <lead>]
        Project lead user id.

  [--boarddefaultAssignee <board><defaultAssignee>]
        Project or compnent default Agileassignee boardfor nameissues. For projects,  [--issue <issue>]
 default is unassigned with options: PROJECT_LEAD or
      Issue key orUNASSIGNED id(blank). For components, default [--toIssue <toIssue>]
    is PROJECT_DEFAULT with options: PROJECT_LEAD, PROJECT_DEFAULT, COMPONENT_LEAD
   Target or link destination issue keyor orUNASSIGNED id(blank).

  [--parentafter <parent><after>]
        ParentVersion issue keyname or id. to add  [--summary <summary>]
        Summary of issuea version after. Defaults to after last version. Use -1 to make it the first version.

  [--priorityboard <priority><board>]
        IssueAgile priorityboard - name or id.

  [--reporterissue <reporter><issue>]
        Issue reporterkey useror id.

  [--assigneetoIssue <assignee><toIssue>]
        IssueTarget assigneeor userlink id.destination Inissue somekey contexts, use -1 for automatic assignment and "" for unassignedor id.

  [--securityparent <security><parent>]
        IssueParent securityissue levelkey name or id.

  [--environmentsummary <environment><summary>]
        IssueSummary of environmentissue.

  [--componentpriority <component><priority>]
        ProjectIssue priority component- name or id.

  [--toComponentreporter <toComponent><reporter>]
        ProjectIssue componentreporter nameuser or id.

  [--componentsassignee <components><assignee>]
        Project components - comma separated names or idsIssue assignee user id. In some contexts, use -1 for automatic assignment and "" for unassigned.

  [--versionsecurity <version><security>]
        Issue Projectsecurity versionlevel name or id.

 or add-on version[--environment <environment>]
        Issue environment.

  [--affectsVersionscomponent <affectsVersions><component>]
        Project component name or id.

Affects versions [- comma separated names-toComponent <toComponent>]
        Project component name or idsid.

  [--fixVersionscomponents <fixVersions><components>]
        FixProject versionscomponents - comma separated names or ids.

  [--customversion <custom><version>]
        AProject version listname ofor customid field key:value pairsor add-on version.
Normally
a comma separated [--affectsVersions <affectsVersions>]
        Affects versions - comma separated names or ids.

  [--fixVersions <fixVersions>]
        Fix versions - comma separated names or ids.

  [--custom <custom>]
        A list of custom field key:value pairs. Normally a comma separated list of colon separated pairs. Key can be field name or
        id. Single quote the key:value pair if it contains a comma (,) or line breaks and similarly for the colon separator. An
        alternative is to use a JSON formatted string to represent the list of key:value pairs.

  [--field <field>]
        Field name or id. For some actions, this parameter must be a custom field.

  [--field2 <field2>]
        Field name or id for a custom field.

  [--fieldExcludes <fieldExcludes>]
        Fields to exclude from cloning - comma separated list of fields.

  [--date <date>]
        Release date for version or due date for issue.

  [--startDate <startDate>]
        Date version was started.

  [--typeissueType <type><issueType>]
        Issue type - name or id. Also, content type for renderRequest and application type.

  [--resolutiontype <resolution><type>]
        ResolutionIssue nametype or (alternative to issueType), custom field type, link type, transition function type, application link type,
        project type, board type, and content type for renderRequest.

  [--resolution <resolution>]
        Resolution name or id.

  [--labels <labels>]
        Labels or tags. A blank separated list.

  [--workflow <workflow>]
        Workflow name.

  [--transition <transition>]
        Workflow transition - name or id.

  [--step <step>]
        Source step name for addTransition.

  [--screen <screen>]
        Transition screen name.

  [--comment <comment>]
        Comment for an issue.

  [--filter <filter>]
        Filter id or favorite filter name. Use for getIssueList is deprecated. Use JQL instead.

  [--jql <jql>]
        JQL query. Alternate way to search for issues for getIssueList and runFromIssueList - continue to use search parameter for
        compatibility with previous.

  [--search <search>]
        Search JQL query using legacy support. Deprecated. Use jql parameter instead for new support.

  [--regex <regex>]
        Regular expression for including matching content. For example, used to subset projects or versions on getProjectList and
        runFromVersionList.

  [--regex2 <regex2>]
        Regular expression for secondary content matching. In some cases, filtering on a secondary field may be needed.

  [--referencelink <reference><link>]
        ReferenceLink todescription. aUsually replacementlink keytype valuename usedfor tolocal rememberlinks lastand createdrelationship issuedescription key or field value from getFieldValue.

  [--link <link>]
        Link description. Usually link type name for local links and relationship description for for remote links.The link id can also
        be used for both linkIssue and deleteLink.

  [--reverseLink <reverseLink>]
        Link description for the (optional) reverse link for addRemoteLink.

  [--value <value>]
        Single field or property value.

  [--values <values>]
        Comma separated list of field values. Single quote values containing commas.

  [--values2 <values2>]
        Comma separated list of field values. Single quote values containing commas.

  [--timeSpent <timeSpent>]
        Time spent on work using. Example: 3h 30m.

  [--estimate <estimate>]
        Estimate of time remaining for an issue. Example: 3h 30m.

  [--originalEstimate <originalEstimate>]
        Original estimate of time to complete work for an issue. Example: 3h 30m.

  [--id <id>]
        Numeric id of an item.

  [--propertyPrefix <propertyPrefix>]
        Prefix used for accessing properties for custom clone actions. Requires Clone Plus [--jsp <jsp>]
        Custom JSP name for clone actions. Deprecatedfor JIRA be installed on the server.

  [--request <request>]
        URL fragment for a request.

  [--requestParameters <requestParameters>]
        URL request parameters or post data..

  [--requestType <requestType>]
        Type of a render request like GET or POST (default: GET)

  [--acceptType <acceptType>]
        Content type to accept for renderRequest if different than type.

  [--limit <limit>]
        Maximum number of entries to return. (default: 2147483647)

  [--apirole <api><role>]
        User role in APIproject
version.
Some requests produce different results based on the api version used. Deprecated. (default: latest)[--group <group>]
        Group name.

  [--roledefaultGroup <role><defaultGroup>]
        UserDefault rolegroup in project

  [--group <group>]
        Group name.

  [--defaultGroup <defaultGroup>]
        Default group to transfer to transfer comment and worklog visibility settings to on removeGroup.

  [--userId <userId>]
        User id for user management and other actions. For some actions, a comma separated list of ids.

  [--newUserId <newUserId>]
        Used to assign a new user id to an existing user. Since JIRA 6.1.

  [--userKey <userKey>]
        Unique internal identifier for user management. Since JIRA 6.1.

  [--userFullName <userFullName>]
        User name for user management actions.

  [--userEmail <userEmail>]
        User email for user management actions.

  [--userPassword <userPassword>]
        User password for user management actions.

  [--autoGroup]
        Groups are automatically added when referenced in add user functions.

  [--permissionScheme <permissionScheme>]
        Permission scheme name or id. (default: Default Permission Scheme)

  [--notificationScheme <notificationScheme>]
        Notification scheme name or id.

  [--issueSecurityScheme <issueSecurityScheme>]
        Issue security scheme name or id

  [--workflowScheme <workflowScheme>]
        Workflow scheme name or id. Use blank for default scheme.

  [--issueTypeScheme <issueTypeScheme>]
        Issue type scheme name or id. Use blank for default scheme.

  [--issueTypeScreenScheme <issueTypeScreenScheme>]
        Issue type screen scheme name or id. Use blank for default scheme. JIRA 5.1 and later only.

  [--fieldConfigurationScheme <fieldConfigurationScheme>]
        Field configuration scheme name or id. Use blank for default scheme.

  [--category <category>]
        Project category. Administrator access required to see or use project categories.

  [--template <template>]
        Project template. JIRA 6.3 and above or shared project key, name, or id (createProject action only). Project template namenames to use (case sensitive) can
as found on the Create project dialog.  be found on the 'Create project' dialog. If a project template is not found, a list of valid templates will be shown in the
error   message.    [ error message.

  [--exportType <exportType>]
        PROJECT to export project information, PARTICIPANTS to export issue participants. Use comman separated list if more than one
        are needed.

  [--login <login>]
        Login token from previous login request.

  [-l|--loginFromStandardInput]
        Get login token from standard input.

  [--functionKey <functionKey>]
        Transition function's unique key. Example: org.swift.jira.cot:createissue-function

  [--targetServer <targetServer>]
        Target server URL for copy requests.

  [--targetUser <targetUser>]
        Target server user. Defaults to user parameter.

  [--targetPassword <targetPassword>]
        Target server user password. Defaults to password parameter.

  [--autoVersion]
        Automatically add versions used in affectsVersions and fixVersions parameters.

  [--autoComponent]
        Automatically add components used in components parameter.

  [--autoAdjust]
        Auto adjust remaining estimate when adding work entry.

  [--asVersion]
        InterpretDeprecated. valuesIgnored parameteron as version values and convert each to the version idJIRA 7.x.

  [--asComponent]
        InterpretDeprecated. valuesIgnored parameteron as component values and convert each to the component id.JIRA 7.x

  [--asCascadeSelect]
        InterpretDeprecatated. valuesIgnored parameteron as a cascade select value idsJIRA 7.x.

  [--appendText]
        Append text to existing value text for description, environment, and single and multi-value custom fields.

  [--subtract]
        Subtract values from existing values custom fields supporting multiple values.

  [--suppressId]
        Suppress showing an id when displaying issue fields on getIssue.

  [--withId]
        Display the issue field value including the internal id (if the field has an internal value) using the following format:
        value (id).

  [--exportAttachments]
        Export attachments and similar data for site export.

  [--copyLinks]
        Copy issue links when cloning an issue.

  [--copyAttachments]
        Copy attachments when cloning an issue.

  [--copyComments]
        Copy comments when cloning an issue.

  [--copyWatchers]
        Copy Watchers when cloning an issue.

  [--copySubtasks]
        Copy subtasks when cloning an issue.

  [--copySubtaskEstimates]
        Copy subtask estimates when cloning an issue.

  [--useParentVersions]
        Copy parent versions to subtask when cloning an issue.

  [--cloneIssues]
        Clone issues when cloning a project.

  [--copyVersions]
        Copy versions when cloning a project.

  [--copyComponents]
        Copy components when cloning a project.

  [--copyRoleActors]
        Copy project role actors when cloning a project.

  [--activate]
        Activate user.

  [--deactivate]
        Deactivate user.

  [--notify]
        Notify user after user is added.

  [--suppressNotify]
        Suppress notifying users when an issue is updated. Initially only available for JIRA Cloud.

  [--includeInactive]
        To include inactive users in a user list.

  [--deleteFilter]
        Attempt to delete the filter associated with the board. Filter must be a findable as a favorite filter.

  [--favorite]
        Mark a filter as a favorite when creating or updating a filter.

  [--lookup]
        Lookup userId via search and validate. An error is reported if search does not return a single user.

  [--legacy]
        Some capabilities have newer impementations (like using newer REST APIs). In some cases, the older (deprecated)
        implementation may still be available for a limited number of releases. This switch can be set to use the older
        implementation to ease migration to the newer support.

  [--preserveCase]
        Some actions (example addUser, addGroup) automatically lowercase names usually because the construct is case insensitive.
        Use this switch to override the default behavior and preserve the case.

  [--helprecursive]
        PrintsInclude subdirectories.
this
help message. [--helpText <helpText>]
Valid actions (case  insensitive):  login - LoginService toDesk: remoteHelp servertext.
Returns
login token. Deprecated starting with JIRA 7.0.
	 Required parameters: password
	 Optional parameters: user
logout - Logout of remote server. Deprecated starting with JIRA 7.0.
getClientInfo - Get information about the this client tool.
	 Optional parameters: outputFormat, file, append, encoding
	 Output formats: 1 - basic, 2 - JVM
getServerInfo - Get information about the JIRA server.
	 Optional parameters: outputFormat, dateFormat, file, append, encoding
	 Output formats: 1 - basic, 2 - detail
validateLicense - Validates the CLI Connector is enabled and licensed on the server.
renderRequest - Render url based request. The response data modified by findReplace processing is returned.
	 Required parameters: request or project or issue
	 Optional parameters: requestParameters, requestType, type, acceptType, findReplace, findReplaceRegex, file, encoding
run - Run actions from a file or standard input.
	 Required parameters: file or standard input [--participants <participants>]
        Service Desk: A comma separated list of user ids for request participation or as organization members.

  [--organization <organization>]
        Service Desk: Organization name or id representing a grouping of users primarily for access permissions.

  [--forUser <forUser>]
        Service Desk: Request is made on behalf of another user.

  [--help]
        Prints this help message.


Valid actions (case insensitive):

login - Login to remote server. Returns login token that can be used on subsequent requests with the login or loginFromStandardInput parameters.
	 Required parameters: password
	 Optional parameters: user
logout - Logout of remote server.
getLoginInfo - Get login information for the current logged in user.
getClientInfo - Get information about the this client tool.
	 Optional parameters: commonoutputFormat, continuefile, simulateappend, clearFileBeforeAppend,encoding
encoding,	 findReplace,Output findReplaceRegexformats: runFromSql1 - Runbasic, actions2 generated- byJVM, SQL11 provided- by the sql parameteraction list, a12 file,- orparameter standardlist
inputgetServerInfo 	- RequiredGet parameters:information sqlabout orthe file or standard inputJIRA server.
	 Optional parameters: commonoutputFormat, driverdateFormat, databasefile, hostappend, encoding
port,	 url, dbUser, dbPassword,
	 propertyFile, continue, simulate, clearFileBeforeAppend, encodingOutput formats: 1 - basic, 2 - detail
validateLicense - Validates the CLI Connector is enabled and licensed on the server.
renderRequest - Render url based request. The response data modified by findReplace processing is returned.
	 Required parameters: request or project or issue
	 Optional parameters: requestParameters, requestType, type, acceptType, findReplace, findReplaceRegex
runFromCsv, file, encoding
run - Run actions generated from a file CSVor standard fileinput.
	 Required parameters: file or standard input
	 Optional parameters: common, propertyFile, continue, quiet, simulate, clearFileBeforeAppend, encoding, findReplace, findReplaceRegex
runFromListrunFromSql - Run actions forgenerated eachby entrySQL inprovided aby list.the 	 Whensql parameter, a file, or standard isinput
provided,	 eachRequired actionparameters: insql theor file augmented by the common parameter will be run for each entry.
	 Otherwise, just the action specified by the common parameter will be run.
	 Available replacement variable is entry or standard input
	 Optional parameters: common, driver, database, host, port, url, dbUser, dbPassword,
	 propertyFile, continue, simulate, clearFileBeforeAppend, encoding, findReplace, findReplaceRegex
runFromCsv - Run actions generated from a CSV file.
	 Required parameters: listfile
	 Optional parameters: filecommon, commonpropertyFile, continue, quiet, simulate, clearFileBeforeAppend, encoding, findReplace, findReplaceRegex
runFromIssueListrunFromList - Run actions for each issueentry fromin an issuea list.
based	 onWhen afile filteris orprovided, aeach search.action Availablein replacementthe variablesfile are project, issue, issueIdaugmented by the common parameter will be run for each entry.
	 Otherwise, just the action specified by the common parameter will be run.
	 Required parameters: filter or jql or search or projectAvailable replacement variables are entry, entry2.
	 Required parameters: list
	 Optional parameters: list2, file, common, continue, quiet, simulate, limitclearFileBeforeAppend, clearFileBeforeAppendencoding, findReplace, findReplaceRegex, file, encoding
runFromProjectList
runFromIssueList - Run actions for each projectissue from withan optionalissue filteringlist bybased leadon anda regexfilter onor projecta keysearch. Available replacement variables are project, issue, projectIdissueId.
	 OptionalRequired parameters: lead,filter regex,or common,jql continue,or simulate,search limit,or clearFileBeforeAppend, project
	 Optional parameters: common, continue, simulate, limit, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding
runFromProjectList - Run actions for each project with optional filtering by lead and regex on project key. Available replacement variables are project, projectId.
	 Optional parameters: lead, regex, common, continue, simulate, limit, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding
runFromVersionList - Run actions for each version in a project. Available replacement variables are project, projectId, version, versionId.
	 Required parameters: project
	 Optional parameters: regex, common, continue, simulate, limit, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding
runFromComponentList - Run actions for each component in a project. Available replacement variables are project, projectId, component, componentId.
	 Required parameters: project
	 Optional parameters: regex, common, continue, simulate, limit, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding
runFromAttachmentList - Run actions for a list of attachments for an issue. Available replacement variables are attachment, attachmentId.
	 Required parameters: issue
	 Optional parameters: common, continue, simulate, limit, regex, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding
runFromGroupList - Run action for each group with optional regex filtering on group name. Available replacement variable is group.
	 Optional parameters: regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding
runFromCommentList - Run action for each comment for an issue with optional regex filtering on the comment body. Available replacement variable is commentId.
	 Required parameters: issue
	 Optional parameters: regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding
runFromRemoteLinkList - Run action for each remote link for an issue with optional filtering defined the same as for getRemoteLinkList.
	 Required parameters: issue
	 Optional parameters: link, regex, regex2, targetUser, targetPassword, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding
getProjectListrunFromUserList - List defined projectsRun action for each user with optionalsimilar filtering byas leadgetUserList. andAvailable regexreplacement onvariable projectis keyuserId.
	 OptionalRequired parameters: lead, regex, outputFormat, file, columns, encodinggroup or name or project and role
	 OutputOptional formatsparameters: 1 - default, 2 - schemes, 999 - all
getProjectCategoryList - List defined project categories.
	 Optional parameters: file, append, columns, encoding
getVersionList - List versions defined for a projectsregex, limit, includeInactive, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding
runFromLinkList - Run action for each issue link for an issue or issues selected by JQL including filtering just like with getLinkList.
	 Required parameters: projectissue or jql
	 Optional parameters: limit, regex, fileoptions, columnscontinue, encodingsimulate, appendclearFileBeforeAppend, outputFormatfindReplace, 	findReplaceRegex, Outputfile, formats:encoding
1getProjectList - default,List 2defined -projects description,with 999optional -filtering allby getComponentListlead -and Listregex componentson defined for a projects.
	 Required parameters: project
project key.
	 Optional parameters: limitlead, regex, outputFormat, file, columns, encoding,
append, outputFormat
	 Output formats: 1 - default, 2 - with projectschemes, 999 - all
getSecurityLevelListgetProjectCategoryList - List security levels defined project categories.
	 Optional parameters: file, append, columns, encoding
getVersionList - List versions defined for a projects.
	 Required parameters: project
	 Optional parameters: regex, file, columns, encoding, append, outputFormat
	 Output formats: 1 - default, 9992 - alldescription, getProjectRoleList999 - Get project roles.
	 Optional parameters: regex, file, append, columns, encoding
getProjectRoleActorList - Get users and groups all
getComponentList - List components defined for a project's roleprojects.
	 Required parameters: project,
role
	 Optional parameters: limit, regex, file, columns, encoding, getProjectRoleByUserListappend, -outputFormat
Get project roles for a user across projects. By default all projects will be included. This action can take a long time to complete depending on number of projects and roles! Requires JIRA 7.0 or higher. Use userId of @all to product a list for all users. Use a regex pattern to subset projects to be included. Each role defines a column with a Yes or No value that indicates if the user is authorize to the project according to the role. This includes either directly authorized as a user or as a member of a group that is authorized. Use columns to subset the roles you want to display.
	 Required parameters: userId
	 Optional parameters: regex, file, append, columns, encoding
getIssueList - List issues for a JQL query, filter, search or by project.
	 Required parameters: filter or jql or search or project
	 Optional parameters: file, dateFormat, limit, withId, suppressId, outputFormat, columns, encoding, append
	 Output formats: 1 - default, 2 or 4 - custom fields, 3 or 4 - security level, 5 - 4 plus time values, 101 - issue keys only, 998 - all except custom, 999 - all
getIssueHistoryList - Get issue change history.
	 Required parameters: issue
	 Optional parameters: file, dateFormat, columns, encoding
getAttachmentList - List attachments for an issue.
	 Required parameters: issue
	 Optional parameters: file, limit, regex, dateFormat, columns, encoding, append, outputFormat
	 Output formats: 1 - default, 999 - all
getCommentList - List of comment information for an issue with regex filtering (JIRA 6.4 and above only) on comment body.
	 Required parameters: issue	 Output formats: 1 - default, 2 - with project, 999 - all
getSecurityLevelList - List security levels defined for a projects.
	 Required parameters: project
	 Optional parameters: file, columns, encoding, append, outputFormat
	 Output formats: 1 - default, 999 - all
getProjectRoleList - Get project roles.
	 Optional parameters: regex, file, append, columns, encoding
getProjectRoleActorList - Get users and groups for a project's role.
	 Required parameters: project, role
	 Optional parameters: file, columns, encoding
getProjectRoleByUserList - Get project roles for a user across projects. By default all projects will be included. This action can take a long time to complete depending on number of projects and roles! Use userId of @all to product a list for all users. Use a regex pattern to subset projects to be included. Each role defines a column with a Yes or No value that indicates if the user is authorize to the project according to the role. This includes either directly authorized as a user or as a member of a group that is authorized. Use columns to subset the roles you want to display.
	 Required parameters: userId
	 Optional parameters: regex, file, append, columns, encoding
getFilterList - Get a list of filters for the current user. On Server or if favorite is specified, the current users favorite filters will be listed. Otherwise, the filters owned by the current user will be listed. Subset the list by regex pattern on the filter name.
	 Optional parameters: favorite, regex, limit
getIssueList - List issues for a JQL query, filter, search or by project.
	 Required parameters: filter or jql or search or project
	 Optional parameters: file, regexdateFormat, limit, outputFormatwithId, suppressId, dateFormatoutputFormat, columns, encoding, append
	 Output formats: 1 - default, 9992 -or all4 getWorkList- -custom Getfields, list3 ofor a4 work- logsecurity entry.level, 	5 Required- parameters:4 issueplus 	time Optionalvalues, parameters:101 dateFormat,- file,issue columns,keys encodingonly, append,998 outputFormat- 	all Outputexcept formats:custom, 999 - all
getVoterListgetIssueHistoryList - Get listissue of users that have voted for an issuechange history.
	 Required parameters: issue
	 Optional parameters: outputFormatfile, append, filedateFormat, columns, encoding
getAttachmentList - List attachments for an issue.
	 Required parameters: issue
	 Optional parameters: file, limit, regex, dateFormat, columns, encoding, append, outputFormat
	 Output formats: 1 - simpledefault, 2999 - CSV,all
999getCommentList - List allof getWatcherListcomment -information Getfor listan ofissue userswith thatregex arefiltering watchingon ancomment issuebody.
	 Required parameters: issue
	 Optional parameters: outputFormat file, regex, limit, appendoutputFormat, filedateFormat, columns, encoding, append
	 Output formats: 1 - simple, 2 - CSVdefault, 999 - all
getLinkListgetWorkList - Get Listlist issueof linksa forwork anlog issueentry.
	 Required parameters: issue
	 Optional parameters: dateFormat, file, columns, encoding, append, getLinkTypeListoutputFormat
-	 GetOutput aformats: list999 of- all
issuegetVoterList link- types.Get 	list Optionalof parameters:users file,that columns,have encodingvoted getCustomFieldListfor -an Getissue.
information	 onRequired allparameters: customissue
fields.
	 Optional parameters: fileoutputFormat, append, file, columns, encoding
getFieldList	 -Output Getformats: information1 on- allsimple, fields.2 Filter by id or name regex.
	 Optional parameters: regex, file, append, columns, encoding
getWorkflowList- CSV, 999 - all
getWatcherList - Get list of users athat workflowsare matchingwatching selectionan criteria.
issue.
	 Required parameters: issue
	 Optional parameters: limitoutputFormat, regex, dateFormatappend, file, append, columns, encoding
getBoardList	 -Output Listformats: Agile1 boards- with optional filtering by regex on name.
	 Optional parameters: regex, file, append, columns, encoding
getIssueTypeList - List issue types valid for a project. If project is blank or @all, all issue types will be listed.
simple, 2 - CSV, 999 - all
getLinkList - List issue links for an issue or issues selected by JQL. Filter by regex pattern matching link name or description. Setting options parameter to one of outward or inward will additionally filter by link direction.
	 Required parameters: issue or jql
	 Optional parameters: project limit, regex, options, file, columns, encoding, append
getStatusListgetLinkTypeList - List statuses Get a list of all issue link types.
	 Optional parameters: file, encodingcolumns, appendencoding
getTransitionListgetCustomFieldList - Get availableinformation workflowon transitionsall forcustom an issue.
	 Required parameters: issue
fields.
	 Optional parameters: outputFormat, file, append, encoding
	 Output formats: 1 - basiccolumns, 2encoding
-getFieldList fields
getAvailableSteps - DeprecatedGet -information getTransitionListon isall recommendedfields. GetFilter availableby workflowid stepsor forname issueregex.
	 RequiredOptional parameters: issue
	 Optional parameters: regex, file, append, columns, encoding
getUserListgetWorkflowList - ListGet userslist fromof a groupworkflows ormatching aselection searchcriteria.
by	 nameOptional fragmentparameters: (userIdlimit, displayregex, namedateFormat, and email). Use name of @all to search for all users. Or use project and role to get all users that are part of the role for the project specified. Email only works if email visibiliity is on and for leading characters only. Include inactive only works for user name searches.
	 Required parameters: group or name or project and role
	 Optional parameters: limit, regex, includeInactive, file, append, columns, encoding
getBoardList - List Agile boards with optional filtering by regex on name.
	 Optional parameters: regex, file, append, columns, encoding
getIssueTypeList - List issue types valid for a project. If project is blank or @all, all issue types will be listed.
	 Optional parameters: project, file, columns, encoding, append,
getStatusList outputFormat- 	List Outputstatuses formats:in 1their -customized basic,order. 2If -project extendedis attributesspecified, 999only -statuses allfor getGroupListvalid -for Getthe aproject listwill of groups with optional filtering by regex on group namebe listed.
	 Optional parameters: limit, regexproject, file, encoding, append
createProjectgetTransitionList - CreateGet aavailable newworkflow projecttransitions withfor key provided by project parameteran issue.
	 Required parameters: project, leadissue
	 Optional parameters: nameoutputFormat, descriptionfile, urlappend, encoding
defaultAssignee,	 lookup, template, permissionScheme, notificationScheme, issueSecurityScheme, 
	workflowScheme, issueTypeScheme, issueTypeScreenScheme, fieldConfigurationScheme, category
updateProject - Update project information. Scheme updates require compatible schemesOutput formats: 1 - basic, 2 - fields
getAvailableSteps - Deprecated - getTransitionList is recommended. Get available workflow steps for issue.
	 Required parameters: projectissue
	 Optional parameters: namefile, descriptionappend, lead,encoding
url,getUserList defaultAssignee,- 	List permissionScheme,users notificationScheme,from issueSecurityScheme,a workflowScheme,group 	or issueTypeScheme,a issueTypeScreenScheme,search fieldConfigurationScheme,by categoryname cloneProjectfragment -(userId, Createdisplay aname, newand projectemail). asUse a clonename of a@all baseto projectsearch (onlyfor issueall security, notification, and permission schemes will be copied to clone, some other fields are also not available to be copied to the clone).
	Optionally copy versions, components, role actors, and issues to new project.
	 Depending on parameters used, issue cloning may require Clone Plus for JIRA - see [CLI Issue Cloning] has more details.
	 Provide a search parameter to subset the issues to be cloned.
	 Required parameters: project, toProject
users. Or use project and role to get all users that are part of the role for the project specified. Email only works if email visibiliity is on and for leading characters only. Include inactive only works for user name searches.
	 Required parameters: group or name or project and role
	 Optional parameters: namelimit, descriptionregex, urlincludeInactive, permissionSchemefile, notificationSchemecolumns, issueSecuritySchemeencoding, 	workflowSchemeappend, issueTypeScheme,outputFormat
issueTypeScreenScheme,	 fieldConfigurationScheme, category,
	 search, type, continue, copyVersions, autoVersion, copyComponents, autoComponent, copyRoleActors, cloneIssues,
	 copyLinks, copyAttachments, copyComments, copyWatchers, copySubtasks, copySubtaskEstimates, useParentVersions,
	 fieldExcludes, propertyPrefix, jsp
deleteProject - Delete a project. Use continue to ignore a not found error.
	 Required parameters: project
	 Optional parameters: continue
getProject - Get project informationOutput formats: 1 - basic, 2 - extended attributes, 999 - all
getGroupList - Get a list of groups with optional filtering by regex on group name.
	 Optional parameters: limit, regex, file, encoding, append
createProject - Create a new project with key provided by project parameter. To share some or all scheme configurations with an existing project, consider using cloneProject or specifying an existing project on the template parameter.
	 Required parameters: project, lead
	 Optional parameters: suppressIdname, filedescription, encodingurl, createBoarddefaultAssignee, -lookup, Createtemplate, anpermissionScheme, Agile board. Type is any support type like scrum, kanban, or diy. Project is a comma separated list of projects identified by key, name, or id.
	 Required parameters: name, type, project
deleteBoard - Delete an Agile board. Use continue to ignore not found errors.
	 Required parameters: id or board
	 Optional parameters: continue
createFilter - Create a filter.
	 Required parameters: name, search
	 Optional parameters: description, favorite
updateFilter - Update a filter by id or filter name (if it is a favorite filter).
	 Required parameters: id of filter
	 Optional parameters: name, search, description, favorite
getFilter - Get information about a filter by id or filter name (if it is a favorite filter)notificationScheme, issueSecurityScheme, 
	workflowScheme, issueTypeScheme, issueTypeScreenScheme, fieldConfigurationScheme, category
updateProject - Update project information. Scheme updates require compatible schemes.
	 Required parameters: project
	 Optional parameters: name, description, lead, url, defaultAssignee,
	 permissionScheme, notificationScheme, issueSecurityScheme, workflowScheme,
	 issueTypeScheme, issueTypeScreenScheme, fieldConfigurationScheme, category
cloneProject - Create a new project as a clone of a base project (only issue security, notification, and permission schemes will be copied to clone, some other fields are also not available to be copied to the clone).
	Parameters specified will override the setting copied from the base project.
	Optionally copy versions, components, role actors, and issues to new project.
	 Provide a search parameter to subset the issues to be cloned.
	 Required parameters: idproject, ortoProject
filter	 deleteFilterOptional -parameters: Deletename, adescription, filterurl, bypermissionScheme, idnotificationScheme, or filter name (if it is a favorite filter). Use continue to ignore not found errors.
	 Required parameters: id or filter
	 Optional parameters: continue
setShareScope - Set current users default share scope for filters. Valid values are GLOBAL and PRIVATE.
	 Required parameters: value
getVersion - Get information for a project version (since JIRA 4.2).
	 Required parameters: project, version
	 Optional parameters: dateFormat, file, encoding
addVersion - Add a new version to a project.
	 Required parameters: project, version
	 Optional parameters: description, after, date, startDate, dateFormat, replace
updateVersion - Update version for a projectissueSecurityScheme,
	workflowScheme, issueTypeScheme, issueTypeScreenScheme, fieldConfigurationScheme, category,
	 search, type, continue, copyVersions, autoVersion, copyComponents, autoComponent, copyRoleActors, cloneIssues,
	 copyLinks, copyAttachments, copyComments, copyWatchers, copySubtasks, copySubtaskEstimates, useParentVersions,
	 fieldExcludes, propertyPrefix
deleteProject - Delete a project. Use continue to ignore a not found error.
	 Required parameters: project
	 Optional parameters: continue
getProject - Get project information.
	 Required parameters: project
	 Optional parameters: suppressId, file, encoding
createBoard - Create an Agile board. Type is any support type like scrum, kanban, or diy. Project is a comma separated list of projects identified by key, name, or id.
	 Required parameters: name, type, project
deleteBoard - Delete an Agile board. Use continue to ignore not found errors.
	 Required parameters: project, versionid or board
	 Optional parameters: name,continue
description,createFilter after,- date,Create startDate, dateFormat, autoVersion
copyVersion - Copy a version from one project to the same project or another projecta filter.
	 Required parameters: name, search
	 Optional parameters: description, favorite
updateFilter - Update a filter by id or filter name (if it is a favorite filter).
	 Required parameters: id project,of versionfilter
	 Optional parameters: toProjectname, namesearch, description, after, date, startDate, dateFormat, replace
copyVersions - Copy all versions from one project to another projectfavorite
getFilter - Get information about a filter by id or filter name (if it is a favorite filter).
	 Required parameters: project,id toProjector 	 Optional parameters: continue, replace
deleteVersionfilter
deleteFilter - Delete a versionfilter fromby aid project.or Updatefilter affectsname and(if fixit versionsis fora issues by removing version reference
	 or swapping it with versions specifiedfavorite filter). Use continue to ignore version not found errorerrors.
	 Required parameters: id project,or versionfilter
	 Optional parameters: affectsVersions, fixVersions, autoVersion, continue
releaseVersionsetShareScope - ReleaseSet acurrent versionusers fordefault ashare project.scope Resets release date if providedfor filters. DefaultsValid tovalues currentare serverGLOBAL date if release date
and PRIVATE.
	 isRequired notparameters: set.value
UsegetVersion continue- toGet ignoreinformation errorfor whema that theproject version is(since already in the correct stateJIRA 4.2).
	 Required parameters: project, version
	 Optional parameters: date, dateFormat, descriptionfile, continueencoding
unreleaseVersionaddVersion - UnreleaseAdd a new version forto a project.
	 Required parameters: project, optionallyversion
reset	 releaseOptional date. Use continue to ignore error when the version is already in the correct stateparameters: description, after, date, startDate, dateFormat, replace
updateVersion - Update version for a project.
	 Required parameters: project, version
	 Optional parameters: datename, dateFormatdescription, descriptionafter, continuedate, archiveVersionstartDate, -dateFormat, ArchiveautoVersion
acopyVersion version- forCopy a project. This hides the version from theone UI. Use continue to ignore error when the version is already in the correct stateproject to the same project or another project.
	 Required parameters: project, version
	 Optional parameters: toProject, name, description, continueafter, unarchiveVersiondate, -startDate, UnarchivedateFormat, areplace
versioncopyVersions for- aCopy project.all Thisversions makesfrom the version visible again in the UI. Use continue to ignore error when the version is already in the correct stateone project to another project.
	 Required parameters: project, versiontoProject
	 Optional parameters: descriptioncontinue, continuereplace
getComponentdeleteVersion - GetDelete information for a componentversion offrom a project.
	 Required parameters: project, component Update affects and fix versions for issues by removing version reference
	 Optionalor parameters:swapping file,it encodingwith addComponentversions -specified. AddUse componentcontinue to a projectignore version not found error.
	 Required parameters: project, componentversion
	 Optional parameters: descriptionaffectsVersions, leadfixVersions, defaultAssigneeautoVersion, replacecontinue
updateComponentreleaseVersion - UpdateRelease a componentversion for a project. 	Resets Requiredrelease parameters:date project,if componentprovided. 	Defaults Optionalto parameters:current name,server description,date lead,if defaultAssigneerelease deleteComponentdate
-	 Deleteis component from a projectnot set. Use continue to ignore component not found error error whem that the version is already in the correct state.
	 Required parameters: project, componentversion
	 Optional parameters: date, dateFormat, description, continue
copyComponentunreleaseVersion - CopyUnrelease a componentversion fromfor onea project, optionally reset release date. Use continue to ignore error when the same project or another projectversion is already in the correct state.
	 Required parameters: project, componentversion
	 Optional parameters: toProjectdate, toComponentdateFormat, name, description, lead,continue
defaultAssignee, replace
copyComponents archiveVersion - CopyArchive alla orversion somefor components from one project to anothera project. This hides the version from the UI. Use continue to ignore error when the version is already in the correct state.
	 Required parameters: project, toProjectversion
	 Optional parameters: componentsdescription, replacecontinue
addProjectRoleActorsunarchiveVersion - AddUnarchive usersa orversion groupsfor to a project role.
	 Required parameters: project, role, userId or group
copyProjectRoleActors - Copy all role actors from a project to another project. This makes the version visible again in the UI. Use continue to ignore error when the version is already in the correct state.
	 Required parameters: project, toProjectversion
	 Optional parameters: description, continue
removeProjectRoleActorsgetComponent - RemoveGet information usersfor ora groupscomponent fromof a project role.
	 Required parameters: project, role,component
userId	 orOptional group
addCustomFieldparameters: file, encoding
addComponent - Add acomponent newto customa fieldproject.
Type must be a valid custom field type key. Optionally, search can be a valid search template key	 Required parameters: project, component
	 Optional parameters: description, lead, defaultAssignee, replace
updateComponent - Update component for a project.
	 Required parameters: fieldproject, typecomponent
	 Optional parameters: name, description, search
removeCustomFieldlead, defaultAssignee
deleteComponent - RemoveDelete acomponent customfrom field by name or ida project. Use continue to ignore acomponent not definedfound error.
	 Required parameters: fieldproject, component
	 Optional parameters: continue
createIssuecopyComponent - CreateCopy a newcomponent issuefrom for aone project orto athe subtasksame ofproject aor parentanother issueproject.
	 Required parameters: typeproject, projectcomponent
or parent
	 Optional parameters: summarytoProject, referencetoComponent, priorityname, reporterdescription, assigneelead, descriptiondefaultAssignee, components, affectsVersions, fixVersions, environment,
	 security, field, value, values, field2, values2, asVersion, asComponent, asCascadeSelect, lookup,
	 date, dateFormat, custom, autoVersion, autoComponent, estimate, originalEstimate, comment, group, role, labels, findReplace, findReplaceRegex, file, encoding
deleteIssue - Delete an issue. Use continue to ignore error if the issue does not existreplace
copyComponents - Copy all or some components from one project to another.
	 Required parameters: project, toProject
	 Optional parameters: components, replace
addProjectRoleActors - Add users or groups to a project role.
	 Required parameters: project, role, userId or group
copyProjectRoleActors - Copy all role actors from a project to another project.
	 Required parameters: issueproject, toProject
	 Optional parameters: continue
cloneIssueremoveProjectRoleActors - CreateRemove ausers newor issuegroups byfrom copyinga anproject existing issuerole.
By	 default,Required ifparameters: the issue is a subtaskproject, role, ituserId willor begroup
clonedaddCustomField to- theAdd samea parent.new Oncustom JIRA 7field.0 andType higher, specifying the parent parameter will allow a subtask to be cloned to a different parent. Some advanced options require Clone Plus for JIRA be installed. [CLI Issue Cloning] has more detailsmust be a valid custom field type key. Optionally, search can be a valid search template key.
	 Required parameters: issuefield, type
	 Optional parameters: parentdescription, type,search
summary,removeCustomField resolution, labels,
	 comment, group, role- Remove a custom field by name or id. Use continue to ignore a not defined error.
	 Required parameters: field
	 Optional parameters: continue
createIssue - Create a new issue for a project or a subtask of a parent issue.
	 Required parameters: issueType or type, project or parent
	 Optional parameters: summary, reference, priority, reporter, assignee, description, components, affectsVersions, fixVersions, environment,
	 security, field, value, values, field2, values2, asVersion, asComponent, asCascadeSelect, lookup,
	 date, dateFormat, custom, autoVersion, autoComponent, estimate, findReplaceoriginalEstimate, findReplaceRegexcomment, filegroup, encodingrole, 	 toProjectlabelsfindReplace, referencefindReplaceRegex, copyLinksfile, copyAttachments,encoding
copyComments, copyWatchers, copySubtasks, copySubtaskEstimates, useParentVersions,
	 fieldExcludes, propertyPrefix, jsp
cloneIssues - Clone issues returned from a JQL search. Advanced options may require the Clone Plus for JIRA be installed. [CLI Issue Cloning] has more detailsdeleteIssue - Delete an issue. Use continue to ignore error if the issue does not exist.
	 Required parameters: jqlissue
	 Optional parameters: toProject,continue
type,cloneIssue continue,- 	Create copyLinks,a copyAttachments,new copyComments,issue copyWatchers,by copySubtasks,copying copySubtaskEstimates,an useParentVersions,existing 	issue. autoVersion,By autoComponentdefault, fieldExcludes,if propertyPrefix,the jspissue updateIssueis -a Updatesubtask, anit existingwill issue. Use appendTextbe cloned to appendthe thesame parameter value to for parent. Specifying the descriptionparent andparameter environmentwill fields.allow Usea appendsubtask to modifybe thecloned fixto versionsa or affects versions fields by their respective valuesdifferent parent.
	 Required parameters: issue
	 Optional parameters: parent, issueType or type, summary, resolution, labels,
	 comment, group, role, priority, reporter, assignee, description, components, affectsVersions, fixVersions, environment,
	 security, field, value, values, field2, values2, asVersion, asComponent, asCascadeSelect, lookup,
	 date, dateFormat, custom, autoVersion, autoComponent, findReplace, estimatefindReplaceRegex, originalEstimatefile, appendencoding,
	 appendTexttoProject, continuereference, suppressNotifycopyLinks, commentcopyAttachments, groupcopyComments, rolecopyWatchers, copySubtasks, findReplacecopySubtaskEstimates, findReplaceRegexuseParentVersions,
file	 fieldExcludes, encodingpropertyPrefix
updateOrCreateIssuecloneIssues - SearchClone forissues anreturned issuefrom usinga JQL search. If[CLI aIssue singleCloning] issuehas is found, update itmore details.
If	 noRequired issue is found, create it.
	 Requiredparameters: jql
	 Optional parameters: jqltoProject, type,issueType project or parent
	 Optional parameters: summarytype, resolutioncontinue,
labels,	 prioritycopyLinks, reportercopyAttachments, assigneecopyComments, descriptioncopyWatchers, componentscopySubtasks, affectsVersionscopySubtaskEstimates, fixVersions, environmentuseParentVersions,
	 securityautoVersion, fieldautoComponent, valuefieldExcludes, values,propertyPrefix
field2,updateIssue values2,- asVersion,Update asComponent,an asCascadeSelect, lookup,
	 date, dateFormat, custom, autoVersion, autoComponent, estimate, originalEstimate, append, appendText, continue, suppressNotify, comment, group, role, , findReplace, findReplaceRegex, file, encoding
getIssue - Get information about an existing issueexisting issue. Use appendText to append the parameter value to for the description and environment fields. Use append to modify the fix versions or affects versions fields by their respective values.
	 Required parameters: issue
	 Optional parameters: issueType or filetype, dateFormatsummary, asVersionresolution, suppressIdlabels, encoding
	 Output formats: 1 - default, 999 - all
assignIssue - Assign an isssue to a userId. Use @default for userId to set the assignee to the project default. Use blank to set the assignee to null.
	 Required parameters: issue, userId
transitionIssue - Transition issue through workflowpriority, reporter, assignee, description, components, affectsVersions, fixVersions, environment,
	 security, field, value, values, field2, values2, lookup,
	 date, dateFormat, custom, autoVersion, autoComponent, , estimate, originalEstimate, append, appendText, continue, suppressNotify, comment, group, role, findReplace, findReplaceRegex, file, encoding
createOrUpdateIssue - Search for an issue using JQL. If a single issue is found, update it. If no issue is found, create it. Formerly known as updateOrCreateIssue (deprecated).
	 Required parameters: issuejql, issueType transition, continueor type, project or parent
	 Optional parameters: type, summary, resolution, labels,
	 priority, reporter, assignee, description, components, affectsVersions, fixVersions, environment,
	 security, field, value, values, field2, values2, asVersion, asComponent, asCascadeSelect, lookup,
	 date, dateFormat, custom, autoVersion, autoComponent, estimate, originalEstimate, append, appendText, continue, suppressNotify, comment, group, role, , findReplace, findReplaceRegex, file, encoding
progressIssuecreateOrUpdateIssue - Progress (transition) issue through workflow. Deprecated in favor of transitionIssue which uses better terminology Search for an issue using JQL. If a single issue is found, update it. If no issue is found, create it. Formerly known as updateOrCreateIssue (deprecated).
	 Required parameters: jql, issueType or type, project or parent
	 Optional parameters: summary, resolution, labels, priority, reporter, assignee, description, components, affectsVersions, fixVersions, environment,
	 security, field, value, values, field2, values2, lookup,
	 date, dateFormat, custom, autoVersion, autoComponent, estimate, originalEstimate, append, appendText, continue, suppressNotify, comment, group, role, findReplace, findReplaceRegex, file, encoding
getIssue - Get information about an existing issue.
	 Required parameters: issue
	 Optional parameters: file, dateFormat, suppressId, encoding
	 Output formats: 1 - default, 999 - all
assignIssue - Assign an isssue to a userId. Use @default for userId to set the assignee to the project default. Use blank to set the assignee to null.
	 Required parameters: issue, userId
transitionIssue - Transition issue through workflow.
	 Required parameters: issue, transition, continue
	 Optional parameters: issueType or type, summary, resolution, labels,
	 priority, reporter, assignee, description, components, affectsVersions, fixVersions, environment,
	 security, field, value, values, field2, values2, lookup,
	 date, dateFormat, custom, autoVersion, autoComponent, comment, group, role, findReplace, findReplaceRegex, file, encoding
progressIssue - Progress (transition) issue through workflow. Deprecated in favor of transitionIssue which uses better terminology
	 Required parameters: issue, step
	 Optional parameters: issueType or type, summary, resolution, labels,
	 priority, reporter, assignee, description, components, affectsVersions, fixVersions, environment,
	 security, field, value, values, field2, values2, lookup,
	 date, dateFormat, custom, autoVersion, autoComponent, comment, group, role, findReplace, findReplaceRegex, file, encoding
addComment - Add a comment to an issue.
	 Required parameters: issue
	 Optional parameters: comment, group, role, findReplace, findReplaceRegex, file, encoding, dateFormat
removeComment - Remove a comment by id from an issue.
	 Required parameters: issue, id
getComment - Get comment information.
	 Required parameters: issue, id
	 Optional parameters: dateFormat, file, append, encoding
updateComment - Update an existing comment to an issue. Use <at:var at:name="commentBody" /> replacement variable if needed when replacing the comment body.
	 Required parameters: issue
	 Optional parameters: comment, group, role, findReplace, findReplaceRegex, file, encoding
getComments - Get a formatted string of all comment text for an issue.
	 Required parameters: issue
	 Optional parameters: file, dateFormat, encoding
addLabels - Add labels to an issue. Requires labels are available for edit on the issue screen.
	 Required parameters: issue, labels
	 Optional parameters: suppressNotify
removeLabels - Remove labels from an issue. Requires labels are available for edit on the issue screen.
	 Required parameters: issue, labels
	 Optional parameters: suppressNotify
getFieldValue - Get field value for an issue.
	 Required parameters: issue, field
	 Optional parameters: file, dateFormat, reference, withId, suppressId, encoding
setFieldValue - Set field value for an issue. Use appendText to append the value to text field. Use append or subtact to have an array field modified by taking the current value and adding or removing the value specified.
	 Required parameters: issue, field, file or value or values
	 Optional parameters: field2, values2, suppressNotify, appendText, append, subtract, encoding, dateFormat
modifyFieldValue - Modify the current field value for an issue with find replace logic.
	 Required parameters: issue, field, findReplace or findReplaceRegex
	 Optional parameters: dateFormat, autoVersion, autoComponent, suppressNotify
copyFieldValue - Copy field value from an issue to a field of another issue. 
	Warning: only works for fields that can be updated from their text representation.
	 Required parameters: issue, field, toIssue or field2
	 Optional parameters: suppressNotify, append, appendText, encoding, dateFormat
addAttachment - Add an attachment to an issue.
	 Required parameters: issue, file
	 Optional parameters: findReplace, findReplaceRegex, name, encoding
addAttachments - Add multiple attachments to an issue from files in a directory matching a regex pattern.
	 Required parameters: issue, file
	 Optional parameters: recursive, regex, findReplace, findReplaceRegex, name, encoding
getAttachment - Get lastest attachment by name or id for an issue.
	 Required parameters: issue, file
	 Optional parameters: name, encoding
removeAttachment - Remove an attachment from an issue. A single attachment is removed by id or all attachments matching the file name.
	 Required parameters: issue, name or id
copyAttachments - Copy attachments from an issue to another issue.
	 Required parameters: issue, toIssue
	 Optional parameters: name, regex
addWatchers - Add watchers to an issue. A comma separated list of user ids can be specified.
	 Required parameters: issue, step
	 Optional parameters: typeuserId, summarylookup, resolution,continue
labels,removeWatchers 	- priority,Remove reporter,watchers assignee,from description, components, affectsVersions, fixVersions, environment,
	 security, field, value, values, field2, values2, asVersion, asComponent, asCascadeSelect, lookup,
	 date, dateFormat, custom, autoVersion, autoComponent, comment, group, role, , findReplace, findReplaceRegex, file, encoding
addCommentan issue. A comma separated list of user ids can be specified.
	 Required parameters: issue
	 Optional parameters: userId, lookup, continue
addVote - Add a comment to anvote for issue.
	 Required parameters: issue
	 OptionalRequired parameters: comment, group, role, , findReplace, findReplaceRegex, file, encoding, dateFormat
getComment - Get comment informationissue
removeVote - Remove vote from issue.
	 Required parameters: issue
addWork - Add work log entry.
	 Required parameters: issue, idtimeSpent
	 Optional parameters: dateFormatcomment, filedate, appenddateFormat, encodingestimate, updateCommentrole, -group, UpdateautoAdjust
anremoveWork existing- commentRemove towork anlog issueentry.
Use	 <at:varRequired atparameters:name="commentBody" /> replacement variable if needed when replacing the comment body id
updateWork - Update work log entry.
	 Required parameters: id, issue
	 Optional parameters: commenttimeSpent, groupcomment, roledate, dateFormat, findReplaceestimate, findReplaceRegexrole, filegroup, encodingautoAdjust
getCommentslinkIssue - GetLink a formatted string of all comment text for anan issue to another issue.
	 Required parameters: issue, toIssue, link
	 Optional parameters: filecomment, group, dateFormatrole, encoding
addLabelsdeleteLink - AddRemove labelslink to an issue. Requires labels are available for edit on theanother issue screen.
	 Required parameters: issue, labelstoIssue, 	link
Optional parameters: suppressNotify
removeLabels getUser - RemoveGet labelsuser frominformation. anWhen issue.name Requiresis labelsused, arethe availablename forsearch editmust onreturn thea issuesingle screenuser.
	 Required parameters: issue, labels userId or userKey or name
	 Optional parameters: file, suppressNotifyendcoding
getFieldValueaddUser - Get field value for Add a new user. Specify notify to send an issueemail.
	 Required parameters: issueuserId, fielduserEmail
	 Optional parameters: file, dateFormat, reference, asVersion userFullName, withIduserPassword, suppressIdnotify, encodingpreserveCase
setFieldValueaddUserWithFile - SetAdd fieldusers valuefrom forcomma anseparated issuefile. UseDeprecated appendText- touse appendrunFromCsv thesupport valuewith toaddUser text fieldinstead.
Use	 appendRequired orparameters: subtactfile
to	 haveOptional anparameters: arraynotify, fieldpreserveCase, modifiedencoding
byupdateUser taking- theUpdate currentuser valueinformation and adding or removing the value specifiedstatus.
	 Required parameters: issue, field, file or value or valuesuserId or userKey
	 Optional parameters: field2userFullName, values2userEmail, suppressNotifynewUserId, asVersionactivate, asComponent, asCascadeSelect, appendText, append, subtract, encoding, dateFormat
modifyFieldValue - Modify the currnt field value for an issue with find replace logic deactivate
removeUser - Remove a user.
	 Required parameters: userId
removeUserWithFile - Remove users from comma separate file. Deprecated - use runFromCsv support with removeUser instead.
	 Required parameters: issue, field, findReplace or findReplaceRegex
file
	 Optional parameters: dateFormat, autoVersion, autoComponent, suppressNotify
copyFieldValue - Copy field value from an issue to a field of another issue. 
	Warning: only works for fields that can be updated from their text representationencoding
addGroup - Add a new group.
	 Required parameters: group
	 Optional parameters: preserveCase
removeGroup - Remove a group.
	 Required parameters: issue, field, toIssue or field2
group
	 Optional parameters: suppressNotify, asVersion, asComponent, asCascadeSelect, append, appendText, encoding, dateFormat
addAttachmentdefaultGroup
addUserToGroup - Add anuser attachment to ana issuegroup.
	 Required parameters: issueuserId, filegroup
	 Optional parameters: findReplaceautoGroup, findReplaceRegex, name, encoding
getAttachment - Get lastest attachment by name or id for an issue preserveCase
addUserToGroupWithFile - Add users to groups from comma separated file. Deprecated - use runFromCsv support with addUserToGroup instead.
	 Required parameters: issue, file
	 Optional parameters: nameautoGroup, preserveCase, encoding
removeAttachmentremoveUserFromGroup - Remove anuser attachment from ana issuegroup.
A single attachment is removed by id or all attachments matching the file name	 Required parameters: userId, group
removeUserFromGroupWithFile - Remove users from groups from comma separated file. Deprecated - use runFromCsv support with removeUserFromGroup instead.
	 Required parameters: issue, name or id
copyAttachmentsfile
	 Optional parameters: encoding
updateUserProperty - CopyAdd attachmentsor fromupdate ana issue to another issueuser's property.
	 Required parameters: issueuserId, name, toIssuevalue
	 Optional parameters: name, regex
addWatchers - Add watchers to an issue. A comma separated list of user ids can be specified lookup
removeUserProperty - Remove a user's property.
	 Required parameters: userId, name
	 Optional parameters: lookup
getWorkflow - Get workflow information.
	 Required parameters: issueworkflow
	 Optional parameters: userIddateFormat, lookupfile, continueencoding
removeWatchersimportWorkflow - RemoveImport watchersworkflow from an issue. A comma separated list of user ids can be specified XML.
	 Required parameters: workflow, file
	 Optional parameters: description, findReplace, findReplaceRegex, encoding
exportWorkflow - Export workflow to XML.
	 Required parameters: issueworkflow
	 Optional parameters: userId, lookup, continue
addVote - Add vote for issuefile, encoding
deleteWorkflow - Delete an inactive workflow. Inactive means it is not associated with any project.
	 Required parameters: issueworkflow
	 removeVoteOptional -parameters: Removecontinue
voterunFromWorkflowList from- issue.Run 	action Requiredfor parameters:each issueworkflow addWorkwith -regex Addfiltering workon logworkflow entryname. 	Available Requiredreplacement parameters:variable issue,is timeSpentworkflow.
	 Optional parameters: commentregex, limit, continue, datesimulate, dateFormatclearFileBeforeAppend, estimatefindReplace, rolefindReplaceRegex, groupfile, autoAdjustencoding
removeWorkcopyWorkflow - Remove work log entry Copy a workflow to a new workflow with the name provided by the name parameter.
	 Required parameters: workflow, name
	 Optional parameters: iddescription
updateWorkaddTransition - Update work log entry.
	 Required parameters: id, issue
	 Optional parameters: timeSpent, comment, date, dateFormat, estimate, role, group, autoAdjust
linkIssue - Link an issue to another issue Add a transition to a workflow. Use name for the transition name. Step represents the source step and transition the target step which defaults to step. Transition screen defaults to none.
	 Required parameters: issueworkflow, toIssuename, linkstep
	 Optional parameters: commentdescription, group, role, 
deleteLink - Remove link to another issue.
	 Required parameters: issue, toIssue, link
getUser - Get user information. When name is used, the name search must return a single usertransition, screen
addTransitionFunction - Add a transition function (post function or validator type) to a workflow transition.  Function configuration is just field/values pairs and is provided using the same parameters as for setting custom field configuration - custom and related parameters.
	 Required parameters: userIdworkflow, ortransition, userKeystep, orfunctionKey
name
	 Optional parameters: filetype, custom, endcodingfield, addUservalues, -field2, Addvalues2
aassociateWorkflow new- user.Associate Priorworkflow to JIRAa workflow 7scheme.0,
an	 emailRequired isparameters: automaticallyname, sentworkflowScheme
tocreateWorkflowScheme the- user.Create Fora JIRAworkflow 7.0scheme andusing higher,a specify notify to send an emaildefault workflow.
	 Required parameters: userIdname, userEmailworkflow
	 Optional parameters: userFullName, userPassword, notify, preserveCase
addUserWithFile - Add users from comma separated file. Deprecated - use runFromCsv support with addUser insteaddescription
getWorkflowScheme - Get workflow scheme information.
	 Required parameters: filename
	 Optional parameters: notify, preserveCasefile, encoding
updateUserdeleteWorkflowScheme - UpdateDelete useran informationinactive orworkflow statusscheme.
	 Required parameters: userIdid or userKeyname
	 Optional parameters: userFullName, userEmail, newUserId, activate, deactivate
removeUser - Remove a user continue
getWorkflowSchemeList - Get list of a workflow schemes matching selection criteria.
	 RequiredOptional parameters: userIdlimit, removeUserWithFileregex, -file, Removeappend, userscolumns, fromencoding
comma	 separateOutput file.formats: Deprecated1 - use runFromCsv support with removeUser instead.
	 Required parameters: file
	 Optional parameters: encoding
addGroup - Add a new group.
	 Required parameters: groupbasic, 2 - detail
runFromWorkflowSchemeList - Run action for each workflow scheme with regex filtering on workflow scheme name. Available replacement variables are scheme and schemeId.
	 Optional parameters: regex, preserveCaselimit, removeGroupcontinue, -simulate, RemoveclearFileBeforeAppend, a group.
	 Required parameters: group
	 Optional parameters: defaultGroup
addUserToGroup - Add user to a groupfindReplace, findReplaceRegex, file, encoding
getScreenList - Get a list of screens with optional regex filtering on name.
	 RequiredOptional parameters: userIdregex, grouplimit, 	file, Optional parameters: autoGroupencoding, append, preserveCaseclearFileBeforeAppend
addUserToGroupWithFilegetScreenSchemeList - Add users to groups from comma separated file. Deprecated - use runFromCsv support with addUserToGroup instead.
	 Required parameters: file
	 Optional parameters: autoGroup, preserveCase, encoding
removeUserFromGroup - Remove user from a group.
	 Required parameters: userId, group
removeUserFromGroupWithFile - Remove users from groups from comma separated file. Deprecated - use runFromCsv support with removeUserFromGroup instead.
	 Required parameters: file
	 Optional parameters: encoding
updateUserProperty - Add or update a user's property.
	 Required parameters: userId, name, value
	 Optional parameters: lookup
removeUserProperty - Remove a user's property.
	 Required parameters: userId, name
	 Optional parameters: lookup
getWorkflow - Get workflow information.
	 Required parameters: name Get a list of screen schemes with optional regex filtering on name.
	 Optional parameters: regex, limit, file, encoding, append, clearFileBeforeAppend
getIssueTypeScreenSchemeList - Get a list of issue type screen schemes with optional regex filtering on name.
	 Optional parameters: regex, limit, file, encoding, append, clearFileBeforeAppend
getIssueTypeSchemeList - Get a list of issue type schemes with optional regex filtering on name.
	 Optional parameters: regex, limit, file, encoding, append, clearFileBeforeAppend
getFieldConfigurationSchemeList - Get a list of field configuration schemes with optional regex filtering on name.
	 Optional parameters: regex, limit, file, encoding, append, clearFileBeforeAppend
getFieldConfigurationList - Get a list of field configurations with optional regex filtering on name.
	 Optional parameters: dateFormatregex, limit, file, encoding
importWorkflow, append, clearFileBeforeAppend
getPermissionSchemeList - Import workflow from XML.
	 Required parameters: name, file
 Get a list of permission schemes with optional regex filtering on name.
	 Optional parameters: descriptionregex, findReplacelimit, findReplaceRegexfile, encoding
exportWorkflow - Export workflow to XML.
	 Required parameters: name, append, clearFileBeforeAppend
getNotificationSchemeList - Get a list of notification schemes with optional regex filtering on name.
	 Optional parameters: regex, limit, file, encoding
deleteWorkflow, append, clearFileBeforeAppend
getIssueSecuritySchemeList - DeleteGet ana inactivelist workflow.of Inactiveissue meanssecurity itschemes iswith notoptional associatedregex withfiltering anyon projectname.
	 RequiredOptional parameters: regex, namelimit, 	file, Optional parameters: continue
runFromWorkflowListencoding, append, clearFileBeforeAppend
runFromScreenList - Run action for each workflowscreen with optional regex filtering on workflow name. Available replacement variables are variablescreen isand workflowscreenId.
	 Optional parameters: regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding
copyWorkflow - Copy a workflow to a new workflow with the name provided by the name parameter.
	 Required parameters: workflow, name
	 Optional parameters: description
addTransition - Experimental. Add a transition to a workflow. Use name for the transition name. Step represents the source step and transition the target step which defaults to step. Transition screen defaults to none.
	 Required parameters: workflow, name, step
	 Optional parameters: description, transition, screen
addTransitionFunction - Experimental. Add a transition function (post function or validator type) to a workflow transition.  Function configuration is just field/values pairs and is provided using the same parameters as for setting custom field configuration - custom and related parameters.
	 Required parameters: workflow, transition, step, functionKey
	 Optional parameters: type, custom, field, values, field2, values2
associateWorkflow - Associate workflow to a workflow scheme.
	 Required parameters: name, workflowScheme
createWorkflowScheme - Create a workflow scheme using a default workflow.
	 Required parameters: name, workflow
	 Optional parameters: description
getWorkflowScheme - Get workflow scheme information.
	 Required parameters: name
	 Optional parameters: file, encoding
deleteWorkflowScheme - Delete an inactive workflow scheme.
	 Required parameters: name
	 Optional parameters: continue
getWorkflowSchemeList - Get list of a workflow schemes matching selection criteria encoding
runFromScreenSchemeList - Run action for each screen scheme with optional regex filtering on name. Available replacement variables are scheme and schemeId.
	 Optional parameters: regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding
runFromIssueTypeScreenSchemeList - Run action for each issue type screen scheme with optional regex filtering on name. Available replacement variables are scheme and schemeId.
	 Optional parameters: regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding
runFromIssueTypeSchemeList - Run action for each issue type scheme with optional regex filtering on name. Available replacement variables are scheme and schemeId.
	 Optional parameters: regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding
runFromFieldConfigurationSchemeList - Run action for each field configuration scheme with optional regex filtering on name. Available replacement variables are fieldConfiguration and fieldConfigurationId.
	 Optional parameters: regex, limit, continue, simulate, regexclearFileBeforeAppend, filefindReplace, appendfindReplaceRegex, columnsfile, encoding
runFromWorkflowSchemeListrunFromFieldConfigurationList - Run action for each workflowfield schemeconfiguration with optional regex filtering on workflow scheme name. Available replacement variable is workflowSchemevariables are scheme and schemeId.
	 Optional parameters: regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding
getScreenListrunFromPermissionSchemeList - GetRun action afor listeach ofpermission screensscheme with optional regex filtering on name. JIRA 6.4 Available replacement variables are scheme and higherschemeId.
	 Optional parameters: regex, limit, continue, simulate, fileclearFileBeforeAppend, findReplace, encodingfindReplaceRegex, appendfile, clearFileBeforeAppendencoding
runFromScreenListrunFromNotificationSchemeList - Run action for each screennotification scheme with optional regex filtering on name. Available replacement variables are screenId and screenName. JIRA 6.4 are scheme and higherschemeId.
	 Optional parameters: regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding
runFromScreenSchemeListrunFromIssueSecuritySchemeList - Run action for each screenissue security scheme with optional regex filtering on name. Available replacement variables are schemeIdscheme and schemeName. JIRA 6.4 and higherschemeId.
	 Optional parameters: regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding
runFromIssueTypeScreenSchemeListdeleteScreen - RunDelete actiona forscreen eachby issueid.
type	 screenRequired schemeparameters: withid
optional	 regexOptional filteringparameters: oncontinue
name.deleteScreenScheme Available- replacementDelete variablesa arescreen schemeIdscheme andby schemeNameid.
JIRA	 6.4 and higher.Required parameters: id
	 Optional parameters: regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding
runFromIssueTypeSchemeList - Run action for each continue
deleteIssueTypeScreenScheme - Delete an issue type screen scheme by id.
	 Required parameters: id
	 Optional parameters: continue
deleteIssueTypeScheme - Delete an issue type scheme with optional regex filtering on name. Available replacement variables are schemeId and schemeName. JIRA 6.4 and higher.
	 Optional parameters: regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding
deleteScreen by id.
	 Required parameters: id
	 Optional parameters: continue
deleteFieldConfiguration - Delete a field configuration by id.
	 Required parameters: id
	 Optional parameters: continue
deleteFieldConfigurationScheme - Delete a screenfield idconfiguration JIRAscheme 6.4 and higherby id.
	 Required parameters: id
	 Optional parameters: continue
deleteScreenSchemedeletePermissionScheme - Delete a screenpermission scheme by id JIRA 6.4 and higher only.
	 Required parameters: id
	 Optional parameters: continue
deleteIssueTypeScreenSchemedeleteNotificationScheme - Delete ana issuepermission type screen scheme by id JIRA 6.4 and higher.
	 Required parameters: id
	 Optional parameters: continue
deleteIssueTypeSchemedeleteIssueSecurityScheme - Delete an issue typesecurity scheme by id JIRA 6.4 and higher.
	 Required parameters: id
	 Optional parameters: continue
addRemoteLink - Add a remote link to an issue. Name is used instead of title from the UI. Specify a reverseLink value to have a reverse link added where supported.
	 Required parameters: issue, name or link
	 Optional parameters: url, toIssue, reversLinkreverseLink, targetServer, targetUser, targetPassword
removeRemoteLink - Remove a remote link to an issue. Name can be an numeric id, global link id, or a name.
	 Required parameters: issue, name
getRemoteLinkList - Get list of a remote links for an issue with optional regex filtering on the name or global id. Also filter by a specific link description if needed using link parameter. If specified, regex2 filtering will be appied to the application type specific information column.
	 Required parameters: issue
	 Optional parameters: link, limit, regex, regex2, targetUser, targetPassword, outputFormat, file, append, columns, encoding
	 Output formats: 1 - basebasic, 999 - all
getApplicationLinkList - Get list of a application links with optional filtering on application type and regex filtering on the name or url. Example types: jira, confluence.
	 Optional parameters: type, limit, regex, file, append, columns, encoding
exportSite - Create a site export. For server, data is put into a file in the JIRA home/export directory. For Cloud, data is put into a JIRA defined file on the associated webdav server - the file can optionally be copied to a local file if the file parameter is specified and permissions allow. Also for Cloud only, use the exportAttachments parameter to request the export contain attachments and similar data.
	 Optional parameters: file, exportAttachments
restoreExport - Restore export from file in the JIRA home/import directory.
	 Required parameters: file
exportData - Experimental - export project or issue participant data in a CLI compatible format.
	 Required parameters: project or search
	 Optional parameters: file, exportType, dateFormat, encoding, search, limit