...
For more information about the problem, including examples/scenarios of the issue level permissions, please visit the mentioned aforementioned JIRA issue at https://gebsun.atlassian.net/browse/HTT-23
Checking permissions
Following commands can be used to determine project and issue permissions for a user (please replace user, password, jira-url, DEMO and DEMO-1 with your JIRA data):
| Code Block |
|---|
| language | bash |
|---|
| title | Find project permissions |
|---|
|
curl -u user:password -X GET -H "Content-Type: application/json" http://jira-url/rest/api/2/mypermissions?projectKey=DEMO
|
| Code Block |
|---|
| language | bash |
|---|
| title | Find issue permissions |
|---|
|
curl -u user:password -X GET -H "Content-Type: application/json" http://jira-url/rest/api/2/mypermissions?issueKey=DEMO-1 |
The output is in JSON format and contains
| Code Block |
|---|
"WORK_ON_ISSUES":
{
"description": "Ability to log work done against an issue. Only useful if Time Tracking is turned on.",
"havePermission": true,
"id": "20",
"key": "WORK_ON_ISSUES",
"name": "Work On Issues",
"type": "PROJECT"
} |