nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

REST API for Custom field collection

Sunil Singh_8kauzu

Which REST API should be hit to get collection of custom fields. preferably, with Name, Id and Type (Project/Issue etc.), what I could get so far is something like this rest/api/latest/issue/createmeta?expand=projects.issuetypes.fields which gives all projects and their custom fields. but i am looking at some kind of Master API which will give me collection of custom fields.

Accepted answers

Earl McCutcheon

Hello @Sunil Singh ,

It looks like you are following the path of looking up the meta-data for creating issues as detailed in this developer documentation:

JIRA Developer Documentation : JIRA REST API Example - Discovering meta-data for creating issues

However, Following the method described above you would want to iterate per the project you wanted to update or add additional field content to

If you are just looking for a list of the fields check out the following endpoint, I think this may do what you are looking for:

GET /rest/api/3/field

Regards,
Earl

All comments

Earl McCutcheon

Hello @Sunil Singh ,

It looks like you are following the path of looking up the meta-data for creating issues as detailed in this developer documentation:

JIRA Developer Documentation : JIRA REST API Example - Discovering meta-data for creating issues

However, Following the method described above you would want to iterate per the project you wanted to update or add additional field content to

If you are just looking for a list of the fields check out the following endpoint, I think this may do what you are looking for:

GET /rest/api/3/field

Regards,
Earl

Sunil Singh_8kauzu

thanks it really helped. Just to confirm if to bifurcate fields can i use schema ? where it says project/issues etc.

Earl McCutcheon

Hi @Sunil Singh ,

Thanks for the additional question, I was not fully understanding what you asking initially, and the GET /rest/api/3/field option is going to be a master list of all fields across all projects, but it sound like you are looking more for the master list on a single project. Let me know if I am still misreading this one or if this is the case.

So, if you want All fields in a single Project you were on the right track with the Use of the REST endpoint call to GET /rest/api/2/issue/createmeta. But also adding in a project key variable to isolate the project before adding in the expand details on the call to the desired project like this:

/rest/api/2/issue/createmeta?projectKeys=EXAMPLE&expand=projects.issuetypes.fields

Regards,
Earl

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software