What makes difference between normal JIRA-SN integration and JIRA spoke - SN integration?

[Manikantahere]

1.  What is the purpose of doing JIRA integration with SN when we can handle agile and ITSM in ServiceNow itself?
2. What is normal Jira integration and Jira spoke integration??
3. When we go form normal and when we go for Jira spoke integration?
4. Is subscription decides what to choose? 
5. Any example like business scenario's when we will go for flow designer custom action and default available action
   when we are doing integration with JIRA spoke - SN?
6. Any specific resources/articles to handle JIRA Spoke and SN integrations in terms different authentications? 

[Mark Manders · Accepted solution]

1. Experience teaches that teams using Jira are not easily convinced to start working in ServiceNow. The way of working in Jira is different than ServiceNow and getting people to leave their 'this is how we do it'-way of working isn't easy. If you don't have Jira, it's easy to use ServiceNow. Moving from Jira to ServiceNow will be a challenge.

2. Define 'normal Jira integration'? You can just pull/push data, or you can use the spoke that is already configured and more easily implemented. There could be a cost consideration.

3. Define 'normal' (using the spoke will get your implementation done faster, but cost could be a consideration)

4. Yes and no. If the business case allows to change the subscription, or your current subscription suffices.

5. Why would you ever create a custom action when an OOB one is available and does the same? 

6. https://docs.servicenow.com/bundle/washingtondc-integrate-applications/page/administer/integrationhu...

https://docs.servicenow.com/bundle/washingtondc-integrate-applications/page/administer/integrationhu...

[Manikantahere]

5. That's the reason I even want to get clarify my self, I have seen the YouTube video where he has configured custom action in flow designer and used same in the flow. Anyhow as out of curiosity i just want to know any ex when we go for custom action.

2 & 3. Normal integration meaning to say traditional way of doing integrating third party tools using scripted rest APIs or Rest Outbound message. if I want to integrate with JIRA only Jira spoke ? 

[Mark Manders]

5. Creating something custom is something you only do if there is no OOB way to get something done. I don't know the video you saw, but maybe it was on an older version and some kind of action that was needed, didn't exist yet, or there was another reason for it, but that's not something I can answer.

2&3 Really depends on your licensing model. How many transactions to you have and how many do you expect to use? Do you already have integration running on an integration bus of your own, or a third party and can you easily connect through that? One upside to the spoke: it's OOB ServiceNow, so if something breaks, they give support. If you use a third party solution, it depends on the agreements you have with the third party.

[Josh Gold]

True, ServiceNow has powerful capabilities, but Jira remains the dominant tool for many software development teams. Integrating the two can help:

• • Break Down Silos: Aligns IT service management and development processes, preventing miscommunications and delays.
  • Provide Centralized Oversight: Gives stakeholders in both IT and development a single source of truth faster.

The best place to start for information around Spokes is in the ServiceNow docs.

If you're interested in other solutions, you can set up a no-code 2-way integration for ServiceNow and Jira with Unito.