Planning Jira/ServiceNow integration to create a SN ticket when Jira release is "released"

[Sjoquist, Carl]

Hi - We are planning a Jira/ServiceNow integration to create a SN ticket when Jira release is "released".   We will use MuleSoft for the integration.   The tricky part right now seems to be in handling selection of the CI (configuration item) from SN when in Jira.   There are evidently many (> 50K!) CIs, so the challenge is handling such a large dataset that is also dynamic (changing daily).    Any thoughts or ideas on best approaches?

Thanks!

Carl

[Dhiren Notani_Exalate_ · Accepted solution]

Hi @Sjoquist, Carl ,

If I may ask, what information do you want to sync from Jira to SNow? Do you also want to sync Jira issues to SNow or vice-a-versa?

Thanks, Dhiren

[Sjoquist, Carl]

Hi Dhiren - eventually we need bi-directional integration, but the first step for this project is to create SN tickets that correspond to a release in Jira.

[Dhiren Notani_Exalate_]

Hi @Sjoquist, Carl , thanks for replying to me.

For syncing tickets bi-directionally you can try an integration solution like Exalate which can help you sync SN tickets with Jira tickets.

You can also synchronize Versions (Release) from Jira from an issue and create SN tickets via Exalate

It provides a script mode which is based on Groovy scripting and provides ultimate level of flexibility and customizability.

Thanks, Dhiren

[Diana_Architect_ZigiWave]

@Sjoquist, Carl hi. I see you've already pointed out Mulesoft as your choice for an integration tool. But, I case you decide to check out other alternatives, take a look at ZigiOps. It's a fully no-code integration solution for bi-directional connection & synchronization of data between systems like Jira and ServiceNow. It reads the schema dynamically & can be customized to fit different use cases (like yours). It does not store any of your data. If you have time and desire, feel free to explore it via demo (free and non-binding) as an alternative.

Regards, Diana (ZigiOps team)