the " Alias ​​connection " field does not appear when I want to create a flow

[nicolaslozano]

Hi experts,

I am creating an integration with Jira, based on the following video and documentation:

• https://www.youtube.com/watch?v=lqnOurQlM_U
• https://developer.servicenow.com/dev.do#!/learn/learning-plans/rome/servicenow_application_developer...

I have done the following steps:

1.) Create a credential:  Here I did a different step than in the video since the token was very long and it wouldn't let me create a "Basic auth" credential so I created an "Api key"

2.)Create a connection: here i did exactly the same as the video

3. Here i checked "Connection & Credential Aliases" in Integration hub:

4.) In flow designer, i created a trigger:

5.) Finally I am ready to create an action: action-Jira-create a issue.

This is where it should show the "connection alias" field but it doesn't.

Thank you for your help.

[Punit S]

Based on the information you provided, it seems like the "connection alias" field is not appearing when creating the  action in ServiceNow Flow Designer. This could be due to a few different reasons, such as a misconfiguration in the Integration Hub or Flow Designer.

Here are a few suggestions to help resolve the issue:

1. Ensure that the Connection Alias exists in Integration Hub: Double-check that you have created the Connection Alias in Integration Hub and that it is properly configured. You can verify this by navigating to the Integration Hub > Connections & Credentials > Connection Aliases and checking that the Jira Connection Alias is present and correctly configured.

2. Ensure that the Connection Alias is associated with the integration action: Check that the Jira Connection Alias is associated with the Jira Create Issue action. You can do this by editing the action and looking for the "Connection Alias" field. If the field is not present, try adding it manually.

3. Check that the action is properly configured: Make sure that you have entered all required fields and that they are properly configured. Double-check the action's documentation for any additional steps or requirements.

4. Try this setup on other sub production instance if you have from scratch : If none of the above steps resolve the issue, try using another ServiceNow instance and you would know if there's any specific issue with instance configuration

If the issue persists after trying these steps, you may want to reach out to the your ServiceNow Services Partner team or Jira support team for further assistance.

Please mark my answer correct/helpful in case it adds value and moves you a step closer to your desired ServiceNow solution goal. 

Thanks,
Punit

[sabaanjum]

Have you find the soultion,if yes please share the solution ,i m facing same issue.

[Sneha R Shinde]

Anyone find the solution, if yes please share the solution. I am facing same issue.

[Rich Little]

This is expected in the new versions of the spoke see the documentation Jira Spoke (servicenow.com)

• Some of the spoke actions from this release onwards don't have the Connection Alias input.

  The existing flows in your instance that use actions of the previous versions, continue to work. However, those earlier actions are renamed by adding the deprecated suffix and you can't use them from this version onwards.

This spoke uses the Jira alias record. To use these actions, you must create a connection record and a credential record and associate them with the Jira alias record.

In Workflow studio view the "Integrations" and search for jira. You will see the record for the sn_jira_spoke connection alias.

Configure this connection and the spoke actions will use it automatically