Jira custom fields not populated in Servicenow flow actions

[Kishor Mudhili]

Hello team,

we are trying to interate between Jira to SN [ Inbound] - we have created few custom fields in Jira , but we canot find the custom fields in Servicenow flow designer action item [ for example in lookup record] , we are using Jira spoke. do we have any limitation to fetch the custom fields.

note: there is no issue from Jira , we have created the fields properly 

[Tanushree Maiti]

Hi @Kishor Mudhili 

If that field with value not present in Response Body , Ask Jira team to double check whether they have included it in request payload before sending it to Servicenow.

[Kishor Mudhili]

anyone having complete jira integration documentation ??

[Tanushree Maiti]

Hi @Kishor Mudhili 

Check these links. Hope it will help you.

https://www.servicenow.com/community/service-management-forum/servicenow-to-jira-bi-directional-inte...

https://www.servicenow.com/community/servicenow-ai-platform-articles/jira-to-servicenow-integration-...

https://youtu.be/37iJjKz94Qw?si=hWc0jPoOeX7uBGoq

https://www.youtube.com/watch?v=q0z8sZ6l3JY&list=PLKH9bPqlw1nfPpLULqorWsRiCKD2nNKUP

https://www.youtube.com/watch?v=37iJjKz94Qw

https://docs.servicenow.com/bundle/xanadu-it-business-management/page/product/agile-jira-integration...

[Vishal36]

Hi @Kishor Mudhili, 

When using the Jira Spoke for inbound integration, custom fields not appearing in Flow Designer is something teams run into occasionally.

You may want to look at a few areas:

• The Jira Spoke does not always expose all custom fields in Flow Designer actions, especially in steps like Lookup Record.
• Some fields are available via the Jira API but aren’t surfaced as data pills unless explicitly supported by the spoke action.
• Field context in Jira (project or issue type scope) can limit what metadata is returned.
• Accessing unsupported fields may require extending the spoke or adding scripted REST logic.

In your case, you may want to explore OpsHub Integration Manager (OIM), a ServiceNow Partner. It connects directly via APIs and supports no-code, plugin-free, bi-directional sync, allowing custom fields to be mapped without relying on Spoke constraints. It also preserves attachments, comments, and inline text context out-of-the-box, avoiding custom scripts. As a ServiceNow Partner, we’ve seen this help teams move beyond native connector limitations.

Hope it helps!