ServiceNow Jira Integration

[devendermanhas]

I am trying to integrate ServiceNow with Jira Server (on‑prem, behind a firewall) using the Jira Spoke. While configuring the Create Issue action, the dynamic fields such as Project ID are not loading and showing errors like “Unable to load dynamic inputs” and “Invalid Connection Alias.” I am currently using the Default Connection, and it seems the issue occurs before the API call is made. I would like to understand if a MID Server and a properly configured Connection Alias are mandatory for this setup and how to correctly configure them.

[pr8172510]

Hi @devendermanhas,

For a Jira Server/Data Center instance hosted on-premises and behind a firewall, a MID Server is generally required for the Jira Spoke to communicate with Jira.

The errors "Unable to load dynamic inputs" and "Invalid Connection Alias" typically indicate that the Jira Spoke cannot establish a valid connection before retrieving dynamic fields such as Project ID, Issue Type, and Custom Fields.

1. Create a dedicated Connection & Credential Alias for Jira.
2. Configure the Jira Server URL and authentication credentials.
3. Associate the connection with a MID Server that has network access to the Jira server.
4. Select this Connection Alias in the Jira Spoke action instead of relying on the Default Connection.
5. Test the connection from the Connection & Credential Alias record.

 Check

• MID Server status = Up and Validated
• Jira REST API reachable from the MID Server
• Connection Alias resolves successfully
• Credentials are valid
• Connection & Credential logs show successful connectivity
  
  https://www.servicenow.com/community/itsm-forum/servicenow-to-jira-integration-on-premise-using-jira...
  
  https://www.servicenow.com/community/developer-forum/jira-spoke-get-editable-fields-dynamic-inputs-f...
  
  
  

[yashkamde]

Hello @devendermanhas ,

share some screenshots from which it will be easy to understand what's happening.

[Tanushree Maiti]

Hi @devendermanhas 

The "Unable to load dynamic inputs" and "Invalid Connection Alias" errors in the ServiceNow Jira Spoke occur because Flow Designer cannot connect to Jira to fetch real-time metadata (like projects or issue types) at design time. To fix this immediately, you must resolve the underlying connection data mismatch or application scope misalignment.

1. 

• Switch your ServiceNow developer session to the Jira Spoke application scope.
• Re-create or re-save your Connection and Credential records within this scope

2.  

• Open Connection & Credential Aliases in ServiceNow.
• Locate the default record for JIRA spoke
• Ensure a valid, active HTTP connection is linked in the related list.
•  If using OAuth 2.0, you must click the Get OAuth Token UI action on the credential record to manually authenticate the first time. If using basic auth/API tokens, ensure your Jira Cloud username is the full email address.

3) 

• Open Workflow Studio / Flow Designer.
• Search for and open the core action causing the error .
• Click Test Action at the top right.
• Supply your Connection Alias, a valid Project Key, and an Issue Type, then click Run Test.
• Once this test succeeds, completely close and reload your original flow to refresh the inputs

4) Ensure  you are using latest version of Jira spoke.