Function getMyPermissions

getMyPermissions(
    client: Client,
    parameters?: {
        commentId?: string;
        issueId?: string;
        issueKey?: string;
        permissions?: string | string[];
        projectConfigurationUuid?: string;
        projectId?: string;
        projectKey?: string;
        projectUuid?: string;
    },
    options?: RequestOptions,
): Promise<{ permissions?: Record<string, any>; [key: string]: unknown }>
Returns a list of permissions indicating which permissions the user has. Details of the user's permissions can be obtained in a global, project, issue or comment context.

The user is reported as having a project permission:
- In the global context, if the user has the project permission in any project.
- For a project, where the project permission is determined using issue data, if the user meets the permission's criteria for any issue in the project. Otherwise, if the user has the project permission in the project.
- For an issue, where a project permission is determined using issue data, if the user has the permission in the issue. Otherwise, if the user has the project permission in the project containing the issue.
- For a comment, where the user has both the permission to browse the comment and the project permission for the comment's parent issue. Only the BROWSE_PROJECTS permission is supported. If a commentId is provided whose permissions does not equal BROWSE_PROJECTS, a 400 error will be returned.
This means that users may be shown as having an issue permission (such as EDIT_ISSUES) in the global context or a project context but may not have the permission for any or all issues. For example, if Reporters have the EDIT_ISSUES permission a user would be shown as having this permission in the global context or the context of a project, because any user can be a reporter. However, if they are not the user who reported the issue queried they would not have EDIT_ISSUES permission for that issue.

For Jira Service Management project permissions, this will be evaluated similarly to a user in the customer portal. For example, if the BROWSE_PROJECTS permission is granted to Service Project Customer - Portal Access, any users with access to the customer portal will have the BROWSE_PROJECTS permission.

Global permissions are unaffected by context.

This operation can be accessed anonymously.

Permissions required: None.
Parameters
- client: Client
- Optionalparameters: {
      commentId?: string;
      issueId?: string;
      issueKey?: string;
      permissions?: string | string[];
      projectConfigurationUuid?: string;
      projectId?: string;
      projectKey?: string;
      projectUuid?: string;
  }
  - OptionalcommentId?: string
    
    The ID of the comment.
  - OptionalissueId?: string
    
    The ID of the issue.
  - OptionalissueKey?: string
    
    The key of the issue. Ignored if issueId is provided.
  - Optionalpermissions?: string | string[]
    
    A list of permission keys. (Required) This parameter accepts a comma-separated list. To get the list of available permissions, use Get all permissions.
  - OptionalprojectConfigurationUuid?: string
  - OptionalprojectId?: string
    
    The ID of project.
  - OptionalprojectKey?: string
    
    The key of project. Ignored if projectId is provided.
  - OptionalprojectUuid?: string
- Optionaloptions: RequestOptions
Returns Promise<{ permissions?: Record<string, any>; [key: string]: unknown }>
- Defined in src/cloud/api/permissions.ts:42