Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Why I can not get list of transitions via the RESR API

My workflow is defined as follows (it is default created by designer):


When I ues browser I can see list of transition:IssueList.jpg

But when I try use TEST API I can not get get list of transition: 


Why I can not get list of transitions via the RESR API?


1 answer

1 accepted

1 vote
Answer accepted

This is counter-intuitive I think and not explained well in the docs, but Issues are not the same thing as Requests.

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.

These two artifacts both have workflow elements.  The workflow for the issue is what you have given us a screenshot of.  The issue will be moved through that workflow by the agent.

But your REST call is trying to fetch the transitions for the request.  These are not the transitions in the issue workflow directly.  They are transitions that your admins have made available to the customer, which then transition the issue as well.  In this case, I suspect you have not made any transitions available to the customer on their requests, so the call to get transitions is returning empty.

Either you'll want to map some transitions for the customer requests, or, if you really do want to work with the issue transitions, use the Jira (Core) api for it - /rest/api/3/issue/{issueIdOrKey}/transitions

KING Answer!!!


Hi @Nic Brough -Adaptavist-  This response is really useful. 

Could you elaborate on "Either you'll want to map some transitions for the customer requests" please?

If you go to configure a request, you'll find it can map the customer request status on to the issues behind it.

Imagine a simple case where your customer service team has to do several things to get a request fixed.  You may have a workflow that represents that process as:

New -> Under investigation -> develop things -> testing -> released -> Done, probably with other status like "with customer for more info" and "cancelled"

Your customers really don't care about half of that flow.  So when the issue is under-investigation, development, being tested, or released into a package, the customer only really needs to know it's with your teams.  So they see a workflow of 

New -> with us -> done  (with with-customer and cancelled too, as diversions from the ideal flow)

Now look at the case where you push an issue into "with customer" because you need them to tell you more.  Instead of having to actively monitor your queues for "customer has responded", you probably want to let the customer push it back to you as they add the information.  So you map a transition in their view of the request, one that lets them push the issue back to your team.

You can do that in the request config.

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events