Discrepancy in Required Fields

[Rotem]

Hi,

I’m integrating my product with Jira Data Center and encountering an issue while trying to identify required fields for creating issues. I’m using the API endpoint:

/rest/api/latest/issue/createmeta/{projectIdOrKey}/issuetypes/{issueTypeId}

Here’s the problem:

• The Component field is marked as required in the Jira UI when creating an issue.
• However, in the schema returned by the API, it is listed with "required": false.
• When I attempt to create a ticket through the API without providing this field, I receive an error indicating that the field is required.

Additional details:

• Jira Environment: Data Center
• Authentication: Bearer token (API key)

How can I reliably determine which fields are truly required for issue creation if the schema doesn’t align with the actual requirements? Is this a known issue, or could it be a misconfiguration in the Jira setup?

Thanks in advance for your help!

[Benjamin]

Hi Rotem,

Could be an API issue. However, before I perform an integration, I usually would validate the process before setting up automation with API calls. That's is the most realiable way to do it based on my own experience. If it can't be done in the UI manually, then it doesn't make sense to start automating. 

A few ways to look at what fields are required is to view the creation screen and look for the red asterisk. The other way is to look at the field configuration scheme to see what is marked for require. The former is much easier and straight forward.

[Rotem]

Hi, thank you for your response.

I’ve confirmed that the field is marked as required in the UI (indicated by the red asterisk), and when I attempt to create an issue without it, the creation fails—further proving it’s a required field.

My issue is that, despite this, the schema returned for this issue type and project specifies the field as "required": false.