How to add new credential and connection in Jira spoke bidirectional integration

[jack33]

Hi All,

I am implementing Jira to ServiceNow bidirectional integration. We have one old credential already created for other Jira project. I have created new credentials for my project. still whenever I try to use any action of Jira, by default old credential get populate in flow designer. How to add new credentials ? 

Thank you in advance.

[Bhuvan]

@jack33 

Follow below documentation steps to add Connections &  Credentials

https://www.servicenow.com/docs/bundle/zurich-it-asset-management/page/product/software-asset-manage...

Go to REST Step where outbound or inbound connection from JIRA is happening and check how credential alias is configured and map it to correct connection alias

See below for reference

If this helped to answer your query, please mark it helpful & accept the solution.

Thanks,

Bhuvan

[Bhuvan]

@jack33 

You can refer below knowledge article to setup Connections & Credentials

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0996141

As per community guidelines, you can accept more than one answer as accepted solution. If my response helped to answer your query, please mark it helpful & accept the solution.

Thanks,

Bhuvan

[jack33]

Hi @Bhuvan  

Thank you for your reply, unfortunately this doesn't help

I am using Jira Spoke, whenever I use any Jira action by default system populate "use default connection" i want to use different connection alias. Is it possible to see multiple connection alias in flow? or where can be configure default connection for jira integration.

Thank you

[Bhuvan]

@jack33 

Go to Flow Designer -> Integrations to see all the Spokes installed. You can see JIRA spoke.

Go to Connections and check for Connections & Credentials configured for JIRA

If you do not want to use default connection alias, you can change from REST Step

Alternate option is to use Define Connection Inline and you can use Credential Alias

If Action is Read-Only and do not have option to change the Connection alias, copy the action and it would allow you to edit it. You can use the new action you created in main flow. Please note this will create a technical debt and is not recommended unless you have a valid use case.

Check why you need to use different connection alias in the first place and see if it is avoidable. If not, you can test above steps and decide accordingly.

If this helped to answer your query, please mark it helpful & accept the solution. 

Thanks,

Bhuvan