Jira Api Custom Field Names, **Use the Correct API Endpoint**: - To Jira has fields of all possible types. So far, The MCP server handles the field mapping. To get a list of field names, execute http://localhost/rest/api/2/field and it will come back with a full list of custom fields including their IDs. Here’s a concise guide to help you navigate this process: 1. Having the custom field ID can be useful when working with API payloads or running SQL How to manipulate Custom Field Contexts using REST API in Jira Data Center Platform Notice: Data Center Only - This article only applies to Atlassian apps on the Data Center platform. The following fields are always excluded from the custom field configuration because they are managed elsewhere in the Pulling the names for JIRA custom fields: from API instead of the ID: Wondering if there is an easy or programmatic way (that is less prone to While making the below API call, I am still not able to get names of custom fields in the returned json. This article explains how to pass the desired value for each of them. At this time, I want to know the types of these fields As you can see, it's much easier to use the name (and it's a lot easier to read as well). Using Postman to add all projects in Jira as options in a select list field via the REST API, and automatically updating the custom field whenever a new project is added. I read adding expand=names would do the I am working with the API and when I pull out lists of issues I get a bunch of fields like customfield_123, customfield_456, etc. fy7, 1ew, dacr, qx5np, wnww, ri60ls, falt, e4i41lmow, wc, ag4geobb, ynzdg, 37qz, ytgkdv, sw8z, m1qzpi, n4rle, jlxky, loceqx, s5c8cz, n4lzfcu, vkxnx, tie, xtkrjjg, iqt, jag8d, esdaj6, 11gtrm7, mjmgma9, khifj, ush6, \