Comments
-
@John Eisenschmidt @chjaway It’s not really a convenient mechanism but you can fetch the workflow via our rest APIs (Rest api) With the XML, what were you using it for?
-
Heya, This is a relatively new API and there are limitations on how much data we maintain, but are you aware of the workflow history API?
-
@Rachel Wright @Darryl Lee On XML export, you are better off looking at JSON returned from the bulk get workflow or workflow search API. The best way to deal with import/export for now is to script this via the create/update APIs. The API's are declarative, so when you say: to me sounds like you'd have to download the…
-
:wave: This recent changelog may be of interest to you. We removed the experimental tags off our public workflow API's last week. They can be used for both company and team scoped workflows. Now in terms of this question of whether there an Atlassian-defined standard transition flow? Not exactly, there's a few common flows…
-
Options: * Rename the transition to something clearer than "To Review". * Remove one of the transitions * Add a condition to hide that transition based on some rules.
-
Hey @Vinod K Gandham, I don't check into community that often. Sorry. The issue is with the statuses in your payload. When no id is supplied we assume you are trying to making a new status with that name. So we are blocking the update because we don't allow you to create a new status with an existing name in the scope of…
-
Heya, it might not be the most beautiful experience, and it's not on Jira server, but there's some limited support for this in JIRA Cloud now. Here's an example where I've set up a required field validators and a regular expression validator together.
