The create issue metadata returned by GET /rest/api/2/issue/createmeta returns fields from the create issue screen (if requested) as a JSON object (indexed by field key). From what I understand JSON object properties have no particular ordering so I am wondering how can I retrieve the fields in the same order as on the issue create screen?
Is there an easy way without having to go through all the schemes and mappings to figure out which is the screen id and then fetch GET /rest/api/2/screens/{screenId}/availableFields? Am I missing something?
@BeataSzturemska any plans to ship some API to fix this? We have an integration with a third party system that renders the create issue screen. While we know from the issue create metadata which fields to render we do not know the order of the fields. Including the field order in the metadata, or in a separate API endpoint would be great.
What’s about storing some useful data (like projectK-issueType-screenID-tabID) in app properties and use them to do a call to /rest/api/3/screens/{screenId}/tabs/{tabId}/fields endpoint.
I suppose these data don’t change so often.