You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I am coding a custom script to integrate a product we use into our JIRA support platform however where I am coming unstuck is with getting the workflow's themselves into the C# application I am writing via the REST API. What I want to avoid is having to maintain a map file for mapping issue types to workflows. Whilst I understand there will always be a degree of maintainability with regards to the code, and configuration, I wish to avoid, and delegate this to intelligent code, as much as possible. I feel like either there is something missing in the REST API for this functionality or I have missed something. What I would like to get is the workflow scheme for the project, the URLs for the workflows (or all of the transitions directly) and then have this part of the program download new versions as and when they are published.
Community moderators have prevented the ability to post new answers.
As no one is able to shed any light on this issue other than Jamie Echlin, and the fact that I have now hard coded the initial configuration schema into my code, I am now shutting this down. The code I have written also updates any out of date workflows however I would have also liked to link back to the schema for any changes there. The solution I am using is an xml configuration file which enables me to do the same thing, albeit manually.
It's simple, there is something missing from the REST APIs. They're not yet complete with respect to the SOAP APIs, and they don't have much in the way of project configuration CRUD stuff.
You can write your own rest api endpoint jira plugin. There are other techniques like screen scraping which I believe the JIRA CLI plugin uses when it can't get info from rest or soap.
Thank you for your response. All I need is the workflow scheme ID which would then spit out what I want:
This ID is what I am after which then gives me the mapping for the issues and the workflow names. I can then use:
This gives me the XML files for the workflows themselves. It's the missing link I am really after: the workflow scheme id.