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

Jira Server/DataCenter Workflow API - finding IDs and details

I'm trying to get info about Jira Server/DataCenter workflows via the API, but am coming up empty.  We are on Jira 8.5.3.

The goal is to find references to Roles in workflow post functions, because the Project Roles View Usage page is wrong/incomplete (

I can  hit rest/api/2/workflow for the list of workflows, but can't then get to rest/api/2/workflow/{id} per the docs because the first call doesn't return IDs.  I was hoping to make the second call work and then see what comes back.  

Has anyone successfully used the Jira 8.x Server API to get detailed info about workflow steps, transitions, functions, etc?

1 answer

0 votes
Daniel Ebers Community Leader Oct 11, 2020

Hi John,

there seems to be no one-click solution available - but as I have seen this question is still unanswered after a month and I had the impression this was discussed earlier I did not want to miss the chance to post this link - just in case it helps.

The answer was (just like to similar questions that come up from time to time regards workflow details) to query "available transitions" using

GET /rest/api/2/issue/{issueIdOrKey}/transitions

which probably not meets the requirement. Additionally there are some comments later on in the linked post - so maybe there is an approach listed there which might be of interest to you even though there is no easy solution available today.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events