To update just the name and description, do not send permissions list at all.

To add or remove a single permission grant instead of updating the whole list at once use the {schemeId}/permission/ resource.

• current assignee - the value of the notificationType is CurrentAssignee
• issue reporter - the value of the notificationType is Reporter
• current user - the value of the notificationType is CurrentUser
• project lead - the value of the notificationType is ProjectLead
• component lead - the value of the notificationType is ComponentLead
• all watchers - the value of the notification type is AllWatchers
• configured user - the value of the notification type is User. Parameter will contain key of the user. Information about the user will be provided if user expand parameter is used.
• configured group - the value of the notification type is Group. Parameter will contain name of the group. Information about the group will be provided if group expand parameter is used.
• configured email address - the value of the notification type is EmailAddress, additionally information about the email will be provided.
• users or users in groups in the configured custom fields - the value of the notification type is UserCustomField or GroupCustomField. Parameter will contain id of the custom field. Information about the field will be provided if field expand parameter is used.
• configured project role - the value of the notification type is ProjectRole. Parameter will contain project role id. Information about the project role will be provided if projectRole expand parameter is used.

Values available for the assigneeType field are: "PROJECT_LEAD" and "UNASSIGNED".

]]>

Results can be ordered by the following fields:

• sequence
• name
• startDate
• releaseDate

• BMP
• GIF
• JPEG
• PNG
• WBMP

 curl \
   -X POST \
   -u admin:admin \
   -H "X-Atlassian-Token: no-check" \
   -H "Content-Type: image/png" \
   --data-binary @mynewavatar.png \
   'http://localhost:8090/jira/rest/api/2/user/avatar/temporary?username=admin&filename=mynewavatar.png'
 

• Delete a user from the role: /rest/api/2/project/{projectIdOrKey}/role/{roleId}?user={username}
• Delete a group from the role: /rest/api/2/project/{projectIdOrKey}/role/{roleId}?group={groupname}

The fields param (which can be specified multiple times) gives a comma-separated list of fields to include in the response. This can be used to retrieve a subset of fields. A particular field can be excluded by prefixing it with a minus.

By default, all (*all) fields are returned in this get-issue resource. Note: the default is different when doing a jql search -- the default there is just navigable fields (*navigable).

• *all - include all fields
• *navigable - include just navigable fields
• summary,comment - include just the summary and comments
• -comment - include everything except comments (the default is *all for get-issue)
• *all,-comment - include everything except comments

The {@code properties} param is similar to {@code fields} and specifies a comma-separated list of issue properties to include. Unlike {@code fields}, properties are not included by default. To include them all send {@code ?properties=*all}. You can also include only specified properties or exclude some properties with a minus (-) sign.

• {@code *all} - include all properties
• {@code *all, -prop1} - include all properties except {@code prop1}
• {@code prop1, prop1} - include {@code prop1} and {@code prop2} properties

• renderedFields - field values in HTML format
• names - display name of each field
• schema - schema for each field which describes a type of the field
• transitions - all possible transitions for the given issue
• operations - all possibles operations which may be applied on issue
• editmeta - information about how each field may be edited. It contains field's schema as well.
• changelog - history of all changes of the given issue
• versionedRepresentations - REST representations of all fields. Some field may contain more recent versions. RESET representations are numbered. The greatest number always represents the most recent version. It is recommended that the most recent version is used. version for these fields which provide a more recent REST representation. After including versionedRepresentations "fields" field become hidden.

• Fields possible for editing are: comment, visibility, started, timeSpent and timeSpentSeconds.
• Either timeSpent or timeSpentSeconds can be set.
• Fields which are not set will not be updated.
• For a request to be valid, it has to have at least one field change.

The number of groups returned is limited by the system property "jira.ajax.autocomplete.limit"

The groups will be unique and sorted.]]>

NB: The above means that for issue-level permissions (EDIT_ISSUE for example), hasPermission may be true when no context is provided, or when a project context is provided, but may be false for any given (or all) issues. This would occur (for example) if Reporters were given the EDIT_ISSUE permission. This is because any user could be a reporter, except in the context of a concrete issue, where the reporter is known.

Global permissions will still be returned for all scopes.

Prior to version 6.4 this service returned project permissions with keys corresponding to com.atlassian.jira.security.Permissions.Permission constants. Since 6.4 those keys are considered deprecated and this service returns system project permission keys corresponding to constants defined in com.atlassian.jira.permission.ProjectPermissions. Permissions with legacy keys are still also returned for backwards compatibility, they are marked with an attribute deprecatedKey=true. The attribute is missing for project permissions with the current keys.

 curl -c cookiejar.txt -X POST -u admin:admin -H "X-Atlassian-Token: no-check" \
   -H "Content-Type: image/png" --data-binary @mynewavatar.png \
   'http://localhost:8090/jira/rest/api/2/user/avatar/temporary?username=admin&filename=mynewavatar.png'

 curl -b cookiejar.txt -X POST -u admin:admin -H "X-Atlassian-Token: no-check" \
   -H "Content-Type: application/json" --data '{"cropperWidth": "65","cropperOffsetX": "10","cropperOffsetY": "16"}' \
   -o tmpid.json \
   http://localhost:8090/jira/rest/api/2/user/avatar?username=admin

 curl -b cookiejar.txt -X PUT -u admin:admin -H "X-Atlassian-Token: no-check" \
   -H "Content-Type: application/json" --data-binary @tmpid.json \
   http://localhost:8090/jira/rest/api/2/user/avatar?username=admin
 

You *must* use "avatar" as the name of the upload parameter:

 curl -c cookiejar.txt -X POST -u admin:admin -H "X-Atlassian-Token: no-check" \
   -F "[email protected];type=image/png" \
   'http://localhost:8090/jira/rest/api/2/user/avatar/temporary?username=admin'