Rest api returns only few possibilities of transitions.
For example:
From atlassian website I can select one from six transitions.
(Escalate, Resolve this issue, Cancel request, Pending, Waiting for customer, In progress)
From API I can select one from three transitions:
(Escalate, Resolve this issue, Cancel request)
Why I can not use (Pending, Waiting for customer, In progress) from Rest Api?
Permissions for API and direct login per browser to Jira are absolutely the same.
This now further suggests, like Nic said, that your workflow contains conditions for some transitions. Have you checked the workflow?
https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/#Advancedworkflowconfiguration-conditions
Please like stated earlier please also check if there are different transitions which named identically but could potentially be restricted by some conditions each.
The above said all under the assumption your user is in a role (Like Service Desk Team, for example) which grants the user the "Transition Issue" permission.
This suggests you are using a different user or a different issue with the rest-api.
An issue in a different status might have different transitions available because of the transitions in the workflow, and a different user might have different permissions because of the conditions on the workflows.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I access to atlassian:
WEB SITE: google account authentication for (user@gmail.com)
REST API: user@gmail.com (same as google account) and API token
From atlassian website I can select one from six transitions.
(Escalate, Resolve this issue, Cancel request, Pending, Waiting for customer, In progress)
From API I can select one from three transitions:
(Escalate, Resolve this issue, Cancel request)
The default configuration at "Jira Service Management Permission Scheme for Project" for "Transition Issues" says:
Project Role (Administrators)
Project Role (atlassian-addons-project-access)
Project Role (Service Desk Team)
Service Project Customer - Portal Access
Where can I set permissions for access user by API token?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
GET /rest/servicedeskapi/request/{issueIdOrKey}/transition
This method returns a list of transitions, the workflow processes that moves a customer request from one status to another, that the user can perform on a request. Use this method to provide a user with a list if the actions they can take on a customer request.
Permissions required: Permission to view the customer request.
App scope required: READ
OAuth scopes required: read:servicedesk-request
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
it's seems that I have the same behaviour; I've seen to this link Solved: Is it possible to transition a Service Desk issue ... (atlassian.com) that they resolved with
rest/api/3/issue/{issue.id}/transitions?expand=transitions.fields
but I don't understand at this time why to use the jira and not service desk api, and why the service desk api does not return the exact list.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, maybe I found the solution here:
Solved: Why I can not get list of transitions via the RESR... (atlassian.com)
"A request is a wrapper around an issue, for the benefit of the customers - customers only see requests, but Agents get to see both the request and the issue behind it."
So, if I use the service desk api I obtain the transitions that customer can use, while I have to us jira api for the entire list that aget use.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.