Is there a way to check the fields configured for an issueType via API?

[Pascal Kiechl]

Howdy,

I probably am missing the forest for the trees here, but I can't seem to figure out if there is a way for me to remotely check for a given project, for a given issueType (e.g. Story), if a given field (e.g. Priority) is configured and included on the 'Create Screen', such that I can use it in a POST method. The API seems quite confusing to me regarding such configurations.

Preferably, this would be done without having to simply try the call and catching the error in case it is not configured.

Also, at the point of the call happening there will be no stories around, so I can't just grab one and check that way.

Cheers,

PK

[Petter Gonçalves]

Hello @Pascal Kiechl

Thank you for reaching out.

Per your description, I understand that you are looking for a REST API that returns the fields added to the "create screen" by setting the issue type in the call. Is that correct?

I'm afraid Jira does not have a REST API call where you can select the issue type to return the fields added to its screens, however, you can return the issues added to a specific screen tab by using the call below:

https://yourdomain.atlassian.net/rest/api/3/screens/{screenId}/tabs/{tabId}/fields

To return all fields on your screen, you would need to add a call like the one above including all the tabs on your screen.

Let us know if I didn't completely understand your request or the call above does not help you achieve what you need.

[Pascal Kiechl]

Hi @Petter Gonçalves 

Thanks for your response.

Yes, you understood my intention correctly. I got the call to work for classic projects (thanks 👍), however it fails for next-gen.

Below a section of the listed screens (GET ... rest/api/3/screens). The ones for the next-gen projects are always displayed with extra information (scope).

using the id 10000, to get the tabs for the screen 'NS: Simple Default Issue Screen", which belongs to a next-gen scrum project, the call (GET ... rest/api/3/screens/{screenID}/tabs) yields a 400 status code.

this does not happen with classic project configurations.

I haven't seen anything in the API documentation, but is it possible that this particular call does not work for next-gen projects or is this something on my end?

Cheers,

PK