JIRA JSON-RPC Scopes
For more information about the JIRA JSON-RPC APIs, please consult the documentation on developer.atlassian.com
and check out the Product API Browser.
RPC calls to the following endpoints are covered:
The required scope for your add-on depends on the methods that your add-on invokes. The table below shows the
required scope for every RPC method call.| Method | Scope |
|---|
createIssue | WRITE |
createIssueWithParent | WRITE |
createIssueWithParentWithSecurityLevel | WRITE |
createIssueWithSecurityLevel | WRITE |
createProject | ADMIN |
createProjectFromObject | ADMIN |
createProjectRole | ADMIN |
deleteProject | ADMIN |
deleteProjectAvatar | PROJECT_ADMIN |
deleteProjectRole | ADMIN |
getAttachmentsFromIssue | READ |
getComment | READ |
getComments | READ |
getComponents | READ |
getFieldsForAction | READ |
getFieldsForCreate | WRITE |
getFieldsForEdit | WRITE |
getGroup | READ |
getIssue | READ |
getIssueById | READ |
getIssueTypesForProject | READ |
getIssuesFromJqlSearch | READ |
getIssuesFromTextSearchWithLimit | READ |
getIssuesFromTextSearchWithProject | READ |
getPriorities | READ |
getProjectAvatar | READ |
getProjectAvatars | READ |
getProjectById | READ |
getProjectByKey | READ |
getProjectsNoSchemes | READ |
getResolutionDateById | READ |
getResolutionDateByKey | READ |
getResolutions | READ |
getSecurityLevel | READ |
getSecurityLevels | WRITE |
getStatuses | READ |
getSubTaskIssueTypesForProject | READ |
getUser | READ |
getVersions | READ |
progressWorkflowAction | WRITE |
setNewProjectAvatar | PROJECT_ADMIN |
setProjectAvatar | PROJECT_ADMIN |
updateIssue | WRITE |
updateProject | PROJECT_ADMIN |
updateProjectRole | ADMIN |