How to add existing Jira OAuth connection as second option in IntegrationHub

[Vincent Lee]

Hi all,

I currently have one Jira instance (let's call it Black) already setup via OAuth 2.0 that I can utilize to send REST calls to.

We have another Jira instance (let's call it Red) that I am trying to have my flow dynamically choose between based on the project selected on a form. The Red instance is setup in Connections & Credentials just like the Black instance: 

However, as seen in the first screenshot, the Red instance is not an available connection and therefore Flow Designer actions run only to the Black instance. The Black connection was added first and is "default" (though I don't see where this is defined).

Following the multiple connections documentation, I attempted to add the existing Red connection, but it appears like it this is setting up a new connection and not adding the existing one. This is using the Jira Spoke essentially out of box. I did need to change the Configuration Template from "Basic Auth with API Key" to "OAuth Authorization Code" since I am using OAuth here.

Any help regarding this would be greatly appreciated!

[Vincent Lee]

Hi @Sankar N , sorry I'm having trouble finding the Authentication section when creating a new action in Flow Designer (last screenshot above). I attempted to create some new steps within the action as well and that didn't seem to help.

As a sided note, I noticed when trying to create a new connection via the tab in Flow Designer, it gets created with the x_bampi_servicecat. prefix.

[Vincent Lee · Accepted solution]

To help any others that may stumble upon this, I was able to get it to work by making the second connection a child alias. I'm not sure if this is the optimal way to do it, but after setting it this way, I am able to manage the connections on a per flow basis. Many of the actions have to be copied to support multiple connections, though.

Introduction to credentials, connections, and aliases (servicenow.com)

[Txilos]

Hi, I'm struggling to make the child alias to work. Basically I'm configuring the same Oauth2.0 steps for the second Jira instance, following the documentation here Set up the Jira spoke for Jira Cloud

but as a child connection to the first one. But I still get the "Warning: A dynamic action error occurred" when selecting the connection in the Jira Spoke action in the flow designer, basically not connecting to the second Jira instance. The default works fine.