MyPermissions
Returns the permissions granted to the current user based on their roles and group memberships.
View-Specific Information
SELECT
The component applies filters server-side only when supported for the specific column and operator, as documented in the Columns section. All other filters are processed client-side.
Jira Cloud
The Jira Cloud API supports both the = and IN operators for the Permission column.For example, the following queries are processed server-side:
SELECT * FROM MyPermissions WHERE Permissions = 'BROWSE_PROJECTS';
SELECT * FROM MyPermissions WHERE Permissions IN ('BROWSE_PROJECTS','EDIT_ISSUES','ADD_COMMENTS');
If Permissions is not specified, the component automatically queries the Permissions table to retrieve the Permissions values. This may result in increased query times.
Columns
| Name | Type | References | SupportedOperators | Platform | Description |
| Id [KEY] | Integer | Common | A unique numeric identifier representing a specific permission available to users in Jira. | ||
| Key [KEY] | String | =,IN | Common | The internal string identifier for the permission, used when managing or referencing permissions through the Application Programming Interface (API) or configuration files. | |
| Name | String | Common | The human-readable name of the permission, indicating the action the permission allows (such as 'Browse Projects' or 'Edit Issues'). | ||
| Type | String | Common | Specifies the scope or context of the permission, such as 'project', 'issue', or 'global', determining where the permission applies. | ||
| Description | String | Common | A detailed explanation of what the permission allows the user to do within the specified scope, providing context for its use. | ||
| HavePermission | Boolean | Common | Indicates whether the current user has this permission in the given context (project, issue, and so on). | ||
| DeprecatedKey | Boolean | Common | Indicates whether the permission key is considered outdated and should not be used in new configurations. |
Pseudocolumns
Pseudocolumn fields are used in the WHERE clause of SELECT statements and offer more granular control over the data returned from the data source.
| Name | Type | Description |
| ProjectKey | String | Filters the permission check to a specific project by its key (for example, 'DEV'), which helps evaluate permissions within that project only. |
| ProjectId | String | Filters the permission check to a specific project by its ID. Used to assess if the user has the permission in that project. |
| IssueKey | String | Filters the permission check to a specific issue by its key (for example, 'DEV-101'), allowing permission evaluation in the context of that issue. |
| IssueId | String | Filters the permission check to a specific issue by its internal numeric ID, used for querying permissions at the issue level. |