Availability

Child pages
  • Documentation

Skip to end of metadata
Go to start of metadata

This page has been renamed to Reference.

On this page

Quick Tips

  • To get all help from a command line use: --help
  • To get help for any action, add --help to the action
    • Example: --action getClientInfo --help
  • More tips

Actions


 

Action

Description

Required Parameters

Optional Parameters

Output Formats

1

Add an attachment to an issue.

issue, file

findReplace, findReplaceRegex, name, encoding

 

2

Add multiple attachments to an issue from files in a directory matching a regex pattern.

issue, file

recursive, regex, findReplace, findReplaceRegex, name, encoding

 

3

Add a comment to an issue.

issue

comment, group, role, findReplace, findReplaceRegex, file, encoding, dateFormat

 

4

Add component to a project.

project, component

description, lead, defaultAssignee, replace

 

5

Add a new custom field. Type must be a valid custom field type key. Optionally, search can be a valid search template key.

field, type

description, search

 

6

Add a new group.

group

preserveCase

 

7

Add labels to an issue. Requires labels are available for edit on the issue screen.

issue, labels

suppressNotify

 

8

Add users or groups to a project role.

project, role, userId or group

 

 

9

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.

issue, name or link

url, toIssue, reverseLink, targetServer, targetUser, targetPassword

 

10

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.

workflow, name, step

description, transition, screen

 

11

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.

workflow, transition, step, functionKey

type, custom, field, values, field2, values2

 

12

Add a new user. Specify notify to send an email.

userId, userEmail

userFullName, userPassword, notify, preserveCase

 

13

Add user to a group.

userId, group

autoGroup, preserveCase

 

14

Add users to groups from comma separated file. Deprecated - use runFromCsv support with addUserToGroup instead.

file

autoGroup, preserveCase, encoding

 

15

Add users from comma separated file. Deprecated - use runFromCsv support with addUser instead.

file

notify, preserveCase, encoding

 

16

Add a new version to a project.

project, version

description, after, date, startDate, dateFormat, replace

 

17

Add vote for issue.

issue

 

 

18

Add watchers to an issue. A comma separated list of user ids can be specified.

issue

userId, lookup, continue

 

19

Add work log entry.

issue, timeSpent

comment, date, dateFormat, estimate, role, group, autoAdjust

 

20

Archive a version for a project. This hides the version from the UI. Use continue to ignore error when the version is already in the correct state.

project, version

description, continue

 

21

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.

issue, userId

 

 

22

Associate workflow to a workflow scheme.

name, workflowScheme

 

 

23

Create a new issue by copying an existing issue. By default, if the issue is a subtask, it will be cloned to the same parent. Specifying the parent parameter will allow a subtask to be cloned to a different parent.

issue

parent, issueType or type, summary, resolution, labels, comment, group, role, priority, reporter, assignee, description, components, affectsVersions, fixVersions, environment, security, field, value, values, field2, values2, lookup, date, dateFormat, custom, autoVersion, autoComponent, findReplace, findReplaceRegex, file, encoding, toProject, reference, copyLinks, copyAttachments, copyComments, copyWatchers, copySubtasks, copySubtaskEstimates, useParentVersions, fieldExcludes, propertyPrefix

 

24

Clone issues returned from a JQL search. CLI Issue Cloning has more details.

jql

toProject, issueType or type, continue, copyLinks, copyAttachments, copyComments, copyWatchers, copySubtasks, copySubtaskEstimates, useParentVersions, autoVersion, autoComponent, fieldExcludes, propertyPrefix

 

25

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.

project, toProject

name, description, url, permissionScheme, notificationScheme, issueSecurityScheme,workflowScheme, issueTypeScheme, issueTypeScreenScheme, fieldConfigurationScheme, category, search, type, continue, copyVersions, autoVersion, copyComponents, autoComponent, copyRoleActors, cloneIssues, copyLinks, copyAttachments, copyComments, copyWatchers, copySubtasks, copySubtaskEstimates, useParentVersions, fieldExcludes, propertyPrefix

 

26

Copy attachments from an issue to another issue.

issue, toIssue

name, regex

 

27

Copy a component from one project to the same project or another project.

project, component

toProject, toComponent, name, description, lead, defaultAssignee, replace

 

28

Copy all or some components from one project to another.

project, toProject

components, replace

 

29

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.

issue, field, toIssue or field2

suppressNotify, append, appendText, encoding, dateFormat

 

30

Copy all role actors from a project to another project.

project, toProject

continue

 

31

Copy a version from one project to the same project or another project.

project, version

toProject, name, description, after, date, startDate, dateFormat, replace

 

32

Copy all versions from one project to another project.

project, toProject

continue, replace

 

33

Copy a workflow to a new workflow with the name provided by the name parameter.

workflow, name

description

 

34

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.

name, type, project

 

 

35

Create a filter.

name, search

description, favorite

 

36

Create a new issue for a project or a subtask of a parent issue.

issueType or type, project or parent

summary, reference, priority, reporter, assignee, description, components, affectsVersions, fixVersions, environment, security, field, value, values, field2, values2, lookup, date, dateFormat, custom, autoVersion, autoComponent, estimate, originalEstimate, comment, group, role, labelsfindReplace, findReplaceRegex, file, encoding

 

37

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).

jql, issueType or type, project or parent

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

 

38

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.

project, lead

name, description, url, defaultAssignee, lookup, template, permissionScheme, notificationScheme, issueSecurityScheme, workflowScheme, issueTypeScheme, issueTypeScreenScheme, fieldConfigurationScheme, category

 

39

Create a workflow scheme using a default workflow.

name, workflow

description

 

40

Delete an Agile board. Use continue to ignore not found errors.

id or board

continue

 

41

Delete component from a project. Use continue to ignore component not found error.

project, component

continue

 

42

Delete a field configuration by id.

id

continue

 

43

Delete a field configuration scheme by id.

id

continue

 

44

Delete a filter by id or filter name (if it is a favorite filter). Use continue to ignore not found errors.

id or filter

continue

 

45

Delete an issue. Use continue to ignore error if the issue does not exist.

issue

continue

 

46

Delete an issue security scheme by id.

id

continue

 

47

Delete an issue type scheme by id.

id

continue

 

48

Delete an issue type screen scheme by id.

id

continue

 

49

Remove link to another issue.

issue, toIssue, link

 

 

50

Delete a permission scheme by id.

id

continue

 

51

Delete a permission scheme by id.

id

continue

 

52

Delete a project. Use continue to ignore a not found error.

project

continue

 

53

Delete a screen by id.

id

continue

 

54

Delete a screen scheme by id.

id

continue

 

55

Delete a version from a project. Update affects and fix versions for issues by removing version reference or swapping it with versions specified. Use continue to ignore version not found error.

project, version

affectsVersions, fixVersions, autoVersion, continue

 

56

Delete an inactive workflow. Inactive means it is not associated with any project.

workflow

continue

 

57

Delete an inactive workflow scheme.

id or name

continue

 

58

Experimental - export project or issue participant data in a CLI compatible format.

project or search

file, exportType, dateFormat, encoding, search, limit

 

59

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.

 

file, exportAttachments

 

60

Export workflow to XML.

workflow

file, encoding

 

61

Get list of a application links with optional filtering on application type and regex filtering on the name or url. Example types: jira, confluence.

 

type, limit, regex, file, append, columns, encoding

 

62

Get lastest attachment by name or id for an issue.

issue, file

name, encoding

 

63

List attachments for an issue.

issue

file, limit, regex, dateFormat, columns, encoding, append, outputFormat

1 - default, 999 - all

64

Deprecated - getTransitionList is recommended. Get available workflow steps for issue.

issue

file, append, encoding

 

65

List Agile boards with optional filtering by regex on name.

 

regex, file, append, columns, encoding

 

66

Get information about this client tool.

 

outputFormat, file, append, encoding

1 - basic, 2 - JVM, 11 - action list, 12 - parameter list

67

Get comment information.

issue, id

dateFormat, file, append, encoding

 

68

List of comment information for an issue with regex filtering on comment body.

issue

file, regex, limit, outputFormat, dateFormat, columns, encoding, append

1 - default, 999 - all

69

Get a formatted string of all comment text for an issue.

issue

file, dateFormat, encoding

 

70

Get information for a component of a project.

project, component

file, encoding

 

71

List components defined for a projects.

project

limit, regex, file, columns, encoding, append, outputFormat

1 - default, 2 - with project, 999 - all

72

Get information on all custom fields.

 

file, append, columns, encoding

 

73

Get a list of field configurations with optional regex filtering on name.

 

regex, limit, file, encoding, append, clearFileBeforeAppend

 

74

Get a list of field configuration schemes with optional regex filtering on name.

 

regex, limit, file, encoding, append, clearFileBeforeAppend

 

75

Get information on all fields. Filter by id or name regex.

 

regex, file, append, columns, encoding

 

76

Get field value for an issue.

issue, field

file, dateFormat, reference, withId, suppressId, encoding

 

77

Get information about a filter by id or filter name (if it is a favorite filter).

id or filter

 

 

78

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.

 

favorite, regex, limit

 

79

Get a list of groups with optional filtering by regex on group name.

 

limit, regex, file, encoding, append

 

80

Get information about an existing issue.

issue

file, dateFormat, suppressId, encoding

1 - default, 999 - all

81

Get issue change history.

issue

file, dateFormat, columns, encoding

 

82

List issues for a JQL query, filter, search or by project.

filter or jql or search or project

file, dateFormat, limit, withId, suppressId, outputFormat, columns, encoding, append

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

83

Get a list of issue security schemes with optional regex filtering on name.

 

regex, limit, file, encoding, append, clearFileBeforeAppend

 

84

List issue types valid for a project. If project is blank or @all, all issue types will be listed.

 

project, file, columns, encoding, append

 

85

Get a list of issue type schemes with optional regex filtering on name.

 

regex, limit, file, encoding, append, clearFileBeforeAppend

 

86

Get a list of issue type screen schemes with optional regex filtering on name.

 

regex, limit, file, encoding, append, clearFileBeforeAppend

 

87

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.

issue or jql

limit, regex, options, file, columns, encoding, append

 

88

Get a list of all issue link types.

 

file, columns, encoding

 

89

Get login information for the current logged in user.

 

 

 

90

Get a list of notification schemes with optional regex filtering on name.

 

regex, limit, file, encoding, append, clearFileBeforeAppend

 

91

Get a list of permission schemes with optional regex filtering on name.

 

regex, limit, file, encoding, append, clearFileBeforeAppend

 

92

Get project information.

project

suppressId, file, encoding

 

93

List defined project categories.

 

file, append, columns, encoding

 

94

List defined projects with optional filtering by lead and regex on project key.

 

lead, regex, outputFormat, file, columns, encoding

1 - default, 2 - schemes, 999 - all

95

Get users and groups for a project's role.

project, role

file, columns, encoding

 

96

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.

userId

regex, file, append, columns, encoding

 

97

Get project roles.

 

regex, file, append, columns, encoding

 

98

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.

issue

link, limit, regex, regex2, targetUser, targetPassword, outputFormat, file, append, columns, encoding

1 - basic, 999 - all

99

Get a list of screens with optional regex filtering on name.

 

regex, limit, file, encoding, append, clearFileBeforeAppend

 

100

Get a list of screen schemes with optional regex filtering on name.

 

regex, limit, file, encoding, append, clearFileBeforeAppend

 

101

List security levels defined for a projects.

project

file, columns, encoding, append, outputFormat

1 - default, 999 - all

102

Get information about the JIRA server.

 

outputFormat, dateFormat, file, append, encoding

1 - basic, 2 - detail

103

List statuses in their customized order. If project is specified, only statuses for valid for the project will be listed.

 

project, file, encoding, append

 

104

Get available workflow transitions for an issue.

issue

outputFormat, file, append, encoding

1 - basic, 2 - fields

105

Get user information. When name is used, the name search must return a single user.

userId or userKey or name

file, endcoding

 

106

List users from a group or a search by name fragment (userId, display name, 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.

group or name or project and role

limit, regex, includeInactive, file, columns, encoding, append, outputFormat

1 - basic, 2 - extended attributes, 999 - all

107

Get information for a project version (since JIRA 4.2).

project, version

dateFormat, file, encoding

 

108

List versions defined for a projects.

project

regex, file, columns, encoding, append, outputFormat

1 - default, 2 - description, 999 - all

109

Get list of users that have voted for an issue.

issue

outputFormat, append, file, columns, encoding

1 - simple, 2 - CSV, 999 - all

110

Get list of users that are watching an issue.

issue

outputFormat, append, file, columns, encoding

1 - simple, 2 - CSV, 999 - all

111

Get workflow information.

workflow

dateFormat, file, encoding

 

112

Get list of a workflows matching selection criteria.

 

limit, regex, dateFormat, file, append, columns, encoding

 

113

Get workflow scheme information.

name

file, encoding

 

114

Get list of a workflow schemes matching selection criteria.

 

limit, regex, file, append, columns, encoding

1 - basic, 2 - detail

115

Get list of a work log entry.

issue

dateFormat, file, columns, encoding, append, outputFormat

999 - all

116

Import workflow from XML.

workflow, file

description, findReplace, findReplaceRegex, encoding

 

117

Link an issue to another issue.

issue, toIssue, link

comment, group, role,

 

118

Login to remote server. Returns login token that can be used on subsequent requests with the login or loginFromStandardInput parameters.

password

user

 

119

Logout of remote server.

 

 

 

120

Modify the current field value for an issue with find replace logic.

issue, field, findReplace or findReplaceRegex

dateFormat, autoVersion, autoComponent, suppressNotify

 

121

Progress (transition) issue through workflow. Deprecated in favor of transitionIssue which uses better terminology

issue, step

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

 

122

Release a version for a project. Resets release date if provided. Defaults to current server date if release date is not set. Use continue to ignore error whem that the version is already in the correct state.

project, version

date, dateFormat, description, continue

 

123

Remove an attachment from an issue. A single attachment is removed by id or all attachments matching the file name.

issue, name or id

 

 

124

Remove a comment by id from an issue.

issue, id

 

 

125

Remove a custom field by name or id. Use continue to ignore a not defined error.

field

continue

 

126

Remove a group.

group

defaultGroup

 

127

Remove labels from an issue. Requires labels are available for edit on the issue screen.

issue, labels

suppressNotify

 

128

Remove users or groups from a project role.

project, role, userId or group

 

 

129

Remove a remote link to an issue. Name can be an numeric id, global link id, or a name.

issue, name

 

 

130

Remove a user.

userId

 

 

131

Remove user from a group.

userId, group

 

 

132

Remove users from groups from comma separated file. Deprecated - use runFromCsv support with removeUserFromGroup instead.

file

encoding

 

133

Remove a user's property.

userId, name

lookup

 

134

Remove users from comma separate file. Deprecated - use runFromCsv support with removeUser instead.

file

encoding

 

135

Remove vote from issue.

issue

 

 

136

Remove watchers from an issue. A comma separated list of user ids can be specified.

issue

userId, lookup, continue

 

137

Remove work log entry.

id

 

 

138

Render url based request. The response data modified by findReplace processing is returned.

request or project or issue

requestParameters, requestType, type, acceptType, findReplace, findReplaceRegex, file, encoding

 

139

Restore export from file in the JIRA home/import directory.

file

 

 

140

Run actions from a file or standard input.

file or standard input

common, continue, simulate, clearFileBeforeAppend, encoding, findReplace, findReplaceRegex

 

141

Run actions for a list of attachments for an issue. Available replacement variables are attachment, attachmentId.

issue

common, continue, simulate, limit, regex, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

142

Run action for each comment for an issue with optional regex filtering on the comment body. Available replacement variable is commentId.

issue

regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

143

Run actions for each component in a project. Available replacement variables are project, projectId, component, componentId.

project

regex, common, continue, simulate, limit, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

144

Run actions generated from a CSV file.

file

common, propertyFile, continue, quiet, simulate, clearFileBeforeAppend, encoding, findReplace, findReplaceRegex

 

145

Run action for each field configuration with optional regex filtering on name. Available replacement variables are scheme and schemeId.

 

regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

146

Run action for each field configuration scheme with optional regex filtering on name. Available replacement variables are fieldConfiguration and fieldConfigurationId.

 

regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

147

Run action for each group with optional regex filtering on group name. Available replacement variable is group.

 

regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

148

Run actions for each issue from an issue list based on a filter or a search. Available replacement variables are project, issue, issueId.

filter or jql or search or project

common, continue, simulate, limit, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

149

Run action for each issue security scheme with optional regex filtering on name. Available replacement variables are scheme and schemeId.

 

regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

150

Run action for each issue type scheme with optional regex filtering on name. Available replacement variables are scheme and schemeId.

 

regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

151

Run action for each issue type screen scheme with optional regex filtering on name. Available replacement variables are scheme and schemeId.

 

regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

152

Run action for each issue link for an issue or issues selected by JQL including filtering just like with getLinkList.

issue or jql

limit, regex, options, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

153

Run actions for each entry in a list. When file is provided, each action in the 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 variables are entry, entry2.

list

list2, file, common, continue, quiet, simulate, clearFileBeforeAppend, encoding, findReplace, findReplaceRegex

 

154

Run action for each notification scheme with optional regex filtering on name. Available replacement variables are scheme and schemeId.

 

regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

155

Run action for each permission scheme with optional regex filtering on name. Available replacement variables are scheme and schemeId.

 

regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

156

Run actions for each project with optional filtering by lead and regex on project key. Available replacement variables are project, projectId.

 

lead, regex, common, continue, simulate, limit, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

157

Run action for each remote link for an issue with optional filtering defined the same as for getRemoteLinkList.

issue

link, regex, regex2, targetUser, targetPassword, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

158

Run action for each screen with optional regex filtering on name. Available replacement variables are screen and screenId.

 

regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

159

Run action for each screen scheme with optional regex filtering on name. Available replacement variables are scheme and schemeId.

 

regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

160

Run actions generated by SQL provided by the sql parameter, a file, or standard input

sql or file or standard input

common, driver, database, host, port, url, dbUser, dbPassword, propertyFile, continue, simulate, clearFileBeforeAppend, encoding, findReplace, findReplaceRegex

 

161

Run action for each user with similar filtering as getUserList. Available replacement variable is userId.

group or name or project and role

regex, limit, includeInactive, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

162

Run actions for each version in a project. Available replacement variables are project, projectId, version, versionId.

project

regex, common, continue, simulate, limit, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

163

Run action for each workflow with regex filtering on workflow name. Available replacement variable is workflow.

 

regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

164

Run action for each workflow scheme with regex filtering on workflow scheme name. Available replacement variables are scheme and schemeId.

 

regex, limit, continue, simulate, clearFileBeforeAppend, findReplace, findReplaceRegex, file, encoding

 

165

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.

issue, field, file or value or values

field2, values2, suppressNotify, appendText, append, subtract, encoding, dateFormat

 

166

Set current users default share scope for filters. Valid values are GLOBAL and PRIVATE.

value

 

 

167

Transition issue through workflow.

issue, transition, continue

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

 

168

Unarchive a version for a project. This makes the version visible again in the UI. Use continue to ignore error when the version is already in the correct state.

project, version

description, continue

 

169

Unrelease a version for a project, optionally reset release date. Use continue to ignore error when the version is already in the correct state.

project, version

date, dateFormat, description, continue

 

170

Update an existing comment to an issue. Use  (commentBody) replacement variable if needed when replacing the comment body.

issue

comment, group, role, findReplace, findReplaceRegex, file, encoding

 

171

Update component for a project.

project, component

name, description, lead, defaultAssignee

 

172

Update a filter by id or filter name (if it is a favorite filter).

id of filter

name, search, description, favorite

 

173

Update an existing 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.

issue

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, , estimate, originalEstimate, append, appendText, continue, suppressNotify, comment, group, role, findReplace, findReplaceRegex, file, encoding

 

174

Update project information. Scheme updates require compatible schemes.

project

name, description, lead, url, defaultAssignee, permissionScheme, notificationScheme, issueSecurityScheme, workflowScheme, issueTypeScheme, issueTypeScreenScheme, fieldConfigurationScheme, category

 

175

Update user information or status.

userId or userKey

userFullName, userEmail, newUserId, activate, deactivate

 

176

Add or update a user's property.

userId, name, value

lookup

 

177

Update version for a project.

project, version

name, description, after, date, startDate, dateFormat, autoVersion

 

178

Update work log entry.

id, issue

timeSpent, comment, date, dateFormat, estimate, role, group, autoAdjust

 

179

Validates the CLI Connector is enabled and licensed on the server.

 

 

 


Parameters

 

Parameter

Short

Value

Description

1

acceptType

 

Content type to accept for renderRequest if different than type.

2

action

a

Requested operation to perform. Valid actions are listed at the end.

3

activate

 

 

Activate user.

4

affectsVersions

 

Affects versions - comma separated names or ids.

5

after

 

Version name or id to add a version after. Defaults to after last version. Use -1 to make it the first version.

6

afterSql

 

SQL to run after a successful action. Limited to specific actions at this time.

7

api

 

API version. Some requests produce different results based on the api version used.

8

append

 

 

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.

9

appendText

 

 

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

10

asCascadeSelect

 

 

Deprecatated. Ignored on JIRA 7.x.

11

asComponent

 

 

Deprecated. Ignored on JIRA 7.x

12

assignee

 

Issue assignee user id. In some contexts, use -1 for automatic assignment and "" for unassigned.

13

asVersion

 

 

Deprecated. Ignored on JIRA 7.x.

14

autoAdjust

 

 

Auto adjust remaining estimate when adding work entry.

15

autoComponent

 

 

Automatically add components used in components parameter.

16

autoGroup

 

 

Groups are automatically added when referenced in add user functions.

17

autoVersion

 

 

Automatically add versions used in affectsVersions and fixVersions parameters.

18

board

 

Agile board name.

19

category

 

Project category. Administrator access required to see or use project categories.

20

clearFileBeforeAppend

 

 

For run actions, this option will automatically clear an existing file on the first append requested.

21

cloneIssues

 

 

Clone issues when cloning a project.

22

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.

23

comment

 

Comment text.

24

common

 

Common parameter string added to all run actions.

25

component

 

Project component name or id.

26

components

 

Project components - comma separated names or ids.

27

connectionTimeout

 

Allow overriding environment settings for connect and read timeouts on URL connections. In milliseconds, 0 means infinite.

28

continue

 

 

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.

29

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.

30

copyAttachments

 

 

Copy attachments when cloning an issue.

31

copyComments

 

 

Copy comments when cloning an issue.

32

copyComponents

 

 

Copy components when cloning a project.

33

copyLinks

 

 

Copy issue links when cloning an issue.

34

copyRoleActors

 

 

Copy project role actors when cloning a project.

35

copySubtaskEstimates

 

 

Copy subtask estimates when cloning an issue.

36

copySubtasks

 

 

Copy subtasks when cloning an issue.

37

copyVersions

 

 

Copy versions when cloning a project.

38

copyWatchers

 

 

Copy Watchers when cloning an issue.

39

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.

40

database

 

Database name is required for SQL actions.

41

date

 

Release date for version or due date for issue.

42

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.

43

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.

44

dbCreateTable

 

 

Database table needs to be created before adding rows.

45

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

46

dbPassword

 

Database user password. Defaults to password.

47

dbTable

 

Database table name when creating or updating a database from list output.

48

dbTableKeys

 

Comma separated list of column names used to access existing rows for update. Normally this defines a primary key set for the table.

49

dbUser

 

Database user name. Defaults to user.

50

deactivate

 

 

Deactivate user.

51

debug

 

 

Requests detail debug output. Optional for all actions.

52

defaultAssignee

 

Project or compnent default assignee for issues. For projects, default is unassigned with options: PROJECT_LEAD or UNASSIGNED (blank). For components, default is PROJECT_DEFAULT with options: PROJECT_LEAD, PROJECT_DEFAULT, COMPONENT_LEAD or UNASSIGNED (blank).

53

defaultGroup

 

Default group to transfer comment and worklog visibility settings to on removeGroup.

54

deleteFilter

 

 

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

55

description

 

Description.

56

driver

 

JDBC driver class or predefined value: postgresql, mysql, mssql, oracle, or db2400. Required for SQL actions.

57

encoding

 

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

58

environment

 

Issue environment.

59

estimate

 

Estimate of time remaining for an issue. Example: 3h 30m.

60

exportAttachments

 

 

Export attachments and similar data for site export.

61

exportType

 

PROJECT to export project information, PARTICIPANTS to export issue participants. Use comman separated list if more than one are needed.

62

favorite

 

 

Mark a filter as a favorite when creating or updating a filter.

63

field

 

Field name or id. For some actions, this parameter must be a custom field.

64

field2

 

Field name or id for a custom field.

65

fieldConfigurationScheme

 

Field configuration scheme name or id. Use blank for default scheme.

66

fieldExcludes

 

Fields to exclude from cloning - comma separated list of fields.

67

file

f

Path to file based content or result output. Use - for standard input.

68

filter

 

Filter id or favorite filter name. Use for getIssueList is deprecated. Use JQL instead.

69

findReplace

 

Find and replace text. Comma separated list of colon separated pairs. Single quote values containing a delimiter. Embedded quotes must be escaped.

70

findReplaceRegex

 

Find and replace text with a regular expression. Comma separated list of colon separated pairs. Single quote values containing a delimiter. Embedded quotes must be doubled.

71

fixVersions

 

Fix versions - comma separated names or ids.

72

forUser

 

Service Desk: Request is made on behalf of another user.

73

functionKey

 

Transition function's unique key. Example: org.swift.jira.cot:createissue-function

74

group

 

Group name.

75

help

 

 

Prints this help message.

76

helpText

 

Service Desk: Help text.

77

host

 

Database host server for SQL actions. Not used if url is provided. Defaults to localhost if not provided.

78

id

 

Numeric id of an item.

79

includeInactive

 

 

To include inactive users in a user list.

80

issue

 

Issue key or id.

81

issueSecurityScheme

 

Issue security scheme name or id

82

issueType

 

Issue type - name or id.

83

issueTypeScheme

 

Issue type scheme name or id. Use blank for default scheme.

84

issueTypeScreenScheme

 

Issue type screen scheme name or id. Use blank for default scheme.

85

jql

 

JQL query. Alternate way to search for issues for getIssueList and runFromIssueList - continue to use search parameter for compatibility with previous.

86

labels

 

Labels or tags. A blank separated list.

87

lead

 

Project lead user id.

88

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.

89

limit

 

Maximum number of entries to return.

90

link

 

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

91

list

 

Comma separated list of entries to populate the entry replacement variable on runFromList. Single quote values containing a delimiter. Embedded quotes must be doubled.

92

list2

 

Comma separated list of entries to populate the entry2 replacement variable on runFromList. Single quote values containing a delimiter. Embedded quotes must be doubled.

93

login

 

Login token from previous login request.

94

loginFromStandardInput

 

 

Get login token from standard input.

95

lookup

 

 

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

96

name

 

Name.

97

newUserId

 

Used to assign a new user id to an existing user.

98

notificationScheme

 

Notification scheme name or id.

99

notify

 

 

Notify user after user is added.

100

options

 

Comma separated list of support, experimental, or other client or action specific options.

101

organization

 

Service Desk: Organization name or id representing a grouping of users primarily for access permissions.

102

originalEstimate

 

Original estimate of time to complete work for an issue. Example: 3h 30m.

103

outputFormat

 

Specify output format for an action.

104

parent

 

Parent issue key or id.

105

participants

 

Service Desk: A comma separated list of user ids for request participation or as organization members.

106

password

p

User password for remote access.

107

permissionScheme

 

Permission scheme name or id.

108

port

 

Database host port for SQL actions. Optional, defaults to database default. Not used if url is provided.

109

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.

110

priority

 

Issue priority - name or id.

111

project

 

Project name, key, or id.

112

propertyFile

 

Property file with database parameters, field mappings, or client specific information.

113

propertyPrefix

 

Prefix used for accessing properties for custom clone actions. Requires Clone Plus for JIRA be installed on the server.

114

quiet

 

 

Limit some output messages. Optional for all actions.

115

recursive

 

 

Include subdirectories.

116

reference

 

Reference to a replacement key value used to remember an action specific value like issue key or similar so it can be referenced later.Each action that allows this parameter will specify what value is being set for the reference replacement key.

117

regex

 

Regular expression for including matching content. For example, used to subset projects or versions on getProjectList and runFromVersionList.

118

regex2

 

Regular expression for secondary content matching. In some cases, filtering on a secondary field may be needed.

119

replace

 

 

Replace existing entity on add, create, or similar actions.

120

reporter

 

Issue reporter user id.

121

request

 

URL fragment for a request.

122

requestParameters

 

URL request parameters or post data..

123

requestType

 

Type of a render request like GET or POST

124

resolution

 

Resolution name or id.

125

reverseLink

 

Link description for the (optional) reverse link for addRemoteLink.

126

role

 

User role in project

127

screen

 

Transition screen name.

128

search

 

Search JQL query using legacy support. Deprecated. Use jql parameter instead for new support.

129

security

 

Issue security level name or id.

130

server

s

Server URL. Normally the base URL of the server and the same as how the server is accessed from a browser.

131

service

 

Service address extension.

132

simulate

 

 

Simulate running actions. Log the action that would be taken.

133

special

 

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

134

sql

 

SQL select statement used to generate a run script.

135

startDate

 

Date version was started.

136

step

 

Source step name for addTransition.

137

subtract

 

 

Subtract values from existing values custom fields supporting multiple values.

138

summary

 

Summary of issue.

139

suppressId

 

 

Suppress showing an id when displaying issue fields on getIssue.

140

suppressNotify

 

 

Suppress notifying users when an issue is updated. Initially only available for JIRA Cloud.

141

targetPassword

 

Target server user password. Defaults to password parameter.

142

targetServer

 

Target server URL for copy requests.

143

targetUser

 

Target server user. Defaults to user parameter.

144

template

 

Project template or shared project key, name, or id (createProject action only). Project template names (case sensitive) can 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.

145

timeSpent

 

Time spent on work. Example: 3h 30m.

146

toComponent

 

Project component name or id.

147

toIssue

 

Target or link destination issue key or id.

148

toProject

 

Project name, key, or id to copy to. For cloning issues, either toProject or project can be used.

149

transition

 

Workflow transition - name or id.

150

type

 

Issue type (alternative to issueType), custom field type, link type, transition function type, application link type, project type, board type, and content type for renderRequest.

151

url

 

Action specific setting. Example: Database access url for SQL actions. Optional when host is provided.

152

useParentVersions

 

 

Copy parent versions to subtask when cloning an issue.

153

user

u

User name for remote access.

154

userEmail

 

User email for user management actions.

155

userFullName

 

User name for user management actions.

156

userId

 

User id for user management and other actions. For some actions, a comma separated list of ids.

157

userKey

 

Unique internal identifier for user management.

158

userPassword

 

User password for user management actions.

159

value

 

Single field or property value.

160

values

 

Comma separated list of field values. Single quote values containing commas.

161

values2

 

Comma separated list of field values. Single quote values containing commas.

162

verbose

 

 

Requests verbose output to help with problem determination. Optional for all actions.

163

version

 

Project version name or id or add-on version.

164

withId

 

 

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

165

workflow

 

Workflow name.

166

workflowScheme

 

Workflow scheme name or id. Use blank for default scheme.

Parameter Tips


Common parameters

A few common parameters are available that are not specifically listed for each action: verbose, debug, quiet, special, dataFormat, dataFormat2.

Tips

  • Use double dash for multi-letter parameters - example: --help
  • Use single dash for single letter parameters indicated in the Short column - example: -v
  • When parameters are specified, most need a value as indicated by a check in the Value column - example: --action addPage
  • Some parameters are flags (boolean) and must not be followed by a value - example: --verbose
  • Parameter names are case sensitive, but, action values are not - example: --userid is invalid but --action addpage is equivalent to --action addPage
  • Some parameters become required once a specific action is chosen. This is indicated in the help text for each action.
  • Some parameters have both short (one letter) and long (more than one letter) parameter names - example: -a or --action are the same and cannot both be specified
  • Some parameters have default values, if so, they are indicated in the help text - example: (default: automation)
  • Some parameters are required - indicated by (...) in the help text - example: (-a|--action) <action>
  • Some parameters are optional - indicated by [...] in the help text - example: [(-f|--file) <file>]
  • Values that contain blanks or some special characters must be enclosed by double quotes - example: --title "this is my title"
  • Quoting rules in commands can vary by environment (sad), here are the techniques that may work in your environment:
    • Many environments: embedded double quotes within a double quoted string can be escaped by doubling the double quote - example: –common "-a addComment --comment ""This is an example of a double quoted string inside a double quote"" "
    • Some environments may need different escaping: embedded double quotes within a double quoted string can be escaped with a \ - example: –common "-a addComment --comment \"This is an example of a double quoted string inside a double quote\" "
    • Run CLI Actions usage: embedded double quotes within a double quoted string can be escaped by doubling the double quote (first example above)
    • A single quote sometimes can used in place of a double quote - example: –common '-a addComment --comment "This is an example of a double quoted string inside a double quote" '
  • Some parameters allow entry of a comma separated list of values, values containing a comma must be enclosed in single quotes - example: --custom "'first:a,b,c', second:x". Embedded single quotes within a quoted string must be doubled
  • Some text fields support the automatic conversion of " \n " (blanks are significant) to be replaced with a new line character - example: --description "A multi-line text field: \n # line 1 \n # line 2"
  • To get help for a specific action (release 5.5 and above), type the action followed by --help - example: --action getProjectList --help

Special parameter

Some special characters are difficult to deal with or make action text very complicated. This is because they have special meaning in either the OS command line handling, the tool's command line parsing, or the tool's use of separators (like comma or colon separated lists). As a convenience to avoid some of these nasty situations, a special parameter was implemented to allow alternate characters to be used instead of (or in addition to) the problematic characters within parameter values. The choice of what special characters to use depends on the content so that you do not have conflicts with intended content. The special parameter works by the user providing a order specific alternate character. The alternative character is replaced with the real character after all other parsing occurs. It is implemented for many action parameters that are problematic in this area. Not all situations are covered, but, that will improve as other use cases are identified.

PositionCharacterCharacter nameSuggested alternateUsage
1,comma Some parameters use comma separated lists.
2:colon#Some parameters use colon separated values.
3@at sign  
4'single quote Used in separated lists to cover cases where content contains separator.
5"double quote~Parameters containing blanks.

A blank in any position is ignored (no alternate provided).

Example: –special " #  ~" provides alternates for colon and double quote. 
         --common "--findReplace ~something to find containing a : (colon)#replacement~"  

Character Set

User and password values should be in the ISO-8859-1 character set. Non standard characters will result in an authorization error similar to: User is not authorized to perform the request.

 

  • No labels