Hey everyone,
I am unable to get correct required field on issue transition
Blocked On is a mandatory field when I transition a task to Blocked state.
However /transitions?expand=transitions.fields ,Transitions GET request does not show it as required field.
If I do a POST transition without Blocked On field response is `400` `Bad Request`
Is there a workaround to know required fields so to make transition via API possible.
I have seen this answer so is there any workaround to know validators for a transition
Thanks a lot
UI with Mandatory blocked on
Transition `GET` response does not show it required
Hi,
The field is not shown as a required field here, because technically the field is not being required within the field configuration scheme. If it was required there, then throughout the entire lifecycle of an issue in Jira, that field would be required to have a value. Instead it appears that this is only being required by the workflow validator, when that issue is transitioned to that next state.
If you were building a Connect App - then you could use the REST API endpoint of
in order to see the validator, conditions, and post functions of that workflow. However that endpoint is restricted to Connect Apps:
Permissions required: Only Connect apps can use this operation.
Connect app scope required:
READ
Aside from that approach, I'm not sure there is a way to use the REST API to learn this about that workflow as an end user. If you were a Jira Admin, you could call the endpoint
This would allow you to see the validators and conditions as well. But for an end user, that isn't typically an option here.
Andy
Thanks a lot, This helps
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.