You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The createmeta endpoint does not return fields in the order they should appear on issue create screens. Based on this question it sounds like a deliberate thing, cynically thinking to try and make more users need JIRA accounts.
The actual create screen in JIRA makes a call to a JSON endpoint when you switch project or issue type in the dropdown so that can be used to get the field order (as well as a heap of other information)
How would you feel about adding a method that uses a URL not in the API docs?
Thank you for a research you've made, but the proposed solution looks too fragile, because:
this isn't officially supported way by JIRA
the URL for a call isn't guaranteed to exist
format of response on that URL isn't guaranteed to be the same
The JIRA UI replication does sound like a very specific thing (people don't do this every day), so for your project you can make such call, but I won't be accepting it into the library.
The createmeta endpoint does not return fields in the order they should appear on issue create screens. Based on this question it sounds like a deliberate thing, cynically thinking to try and make more users need JIRA accounts.
The actual create screen in JIRA makes a call to a JSON endpoint when you switch project or issue type in the dropdown so that can be used to get the field order (as well as a heap of other information)
How would you feel about adding a method that uses a URL not in the API docs?
Proof of concept code snippet:
Annoyingly pid is the project ID and not the text key so it has to be done with two requests.
The text was updated successfully, but these errors were encountered: