Editmeta API returns stale or outdated data for custom field

Forge Forge Modules and Product Triggers
, , ,
1

Morning,

I am having the problem that when doing a GET to the Editmeta Jira API it returns a custom field as editable, even though it is not on the screen anymore.

This might be an edgecase, as this only happens if:

  1. The custom field was added to the screen
  2. The key of the custom field is changed and the app redeployed

Now the screen does not have the custom field anymore, but it still gets returned by the Editmeta API. As the key should not change that often, I hope this will not cause problems for an app deployed to production.

Could this be a bug by the API, or is there another reason that could cause this?

Regards,
Daniel