Hi,
I’d like to share with you my idea how to fetch all fields for classic project.
- You can call
/rest/api/3/issuetypescreenscheme/project?projectId=XXX
to get configured issue type screen scheme ID for that project. - Then you can call
/rest/api/3/issuetypescreenscheme/mapping?issueTypeSchemeId=YYY
to get mappings between issue type screen scheme, issue types and screen schemes. - Now you can check screens for every issue type using
rest/api/3/screenscheme?id=ZZZ
- When you get sum of fields present on all tabs of all screens - create/edit/view/default by calling
/rest/api/3/screens/AAA/tabs/BBB/fields
then you have a list of fields used in project.
Eh, it’s quite complex .
According to my knowledge performing such operations in next-gen project is impossible with currently available APIs.
When it comes to getting custom fields option values including non-global context, it’s something that we keep in mind during planning the next steps of extending project configuration APIs, but I can’t share any exact dates when it will be done.