Hi,
Our app adds new custom field types to Jira. On an issue update trigger, we need to update value of these custom fields. Currently we are fetching all the fields in Jira and then filtering for our own custom fields. We need to get only our own custom fields without fetching all the fields in Jira. There is a get custom field configurations REST API but it requires you to know either the ID or key of the custom field and both of them are not available to us during deployment or development. What is the best way to get only our own custom fields without fetching all the fields from Jira? Why does this endpoint ask for an ID which is not available to APP and dynamically created by Jira, am I missing something here?
Unfortunately I’m afraid you do have indeed to fetch all the custom fields, then you can filter yours using the schema property, which will contain your custom field type key (that you specified in your manifest, so it’s known ahead of time).
Once you have all the field ids, you can then retrieve the configuration objects and the applicable contexts using the API you linked, or the new experimental one, which in my experience seems to be working quite well.
1 Like