The "Known Limitations" in https://support.atlassian.com/rovo/docs/getting-started-with-the-atlassian-remote-mcp-server/ says: * Custom Jira fields may not be recognized or returned without explicit setup. Can you elaborate on this? * What are the conditions in which custom fields are not recognized or returned? * What explicit setup is required to ensure the MCP can see the custom fields? Without native custom field support, we are forced to use a 3rd party Jira MCP like https://github.com/fkesheh/jira-mcp-server which is not ideal.

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; } } }

Atlassian MCP custom field support

Jarrod Spurrier

The "Known Limitations" in https://support.atlassian.com/rovo/docs/getting-started-with-the-atlassian-remote-mcp-server/ says:

Custom Jira fields may not be recognized or returned without explicit setup.

Can you elaborate on this?

What are the conditions in which custom fields are not recognized or returned?
What explicit setup is required to ensure the MCP can see the custom fields?

Without native custom field support, we are forced to use a 3rd party Jira MCP like https://github.com/fkesheh/jira-mcp-server which is not ideal.

Accepted answers

All comments

Benjamin_tmh9yg

Hi @Jarrod Spurrier

May need to contact Atlassian support directly since this is in Beta to get the details.. Usually, when I encounter any software in Beta, it usually something "just to try/test out" but would not rely on it like I would for a General available release.