ServiceNow to Jira: Agile 2.0

[Matthew Wigglesworth]

We are trying to set up the ServiceNow Agile 2.0 to Jira integration. 

While we are able to import the Jira issues as stories in ServiceNow, when creating a new story in ServiceNow for a specific group it is creating duplicated issues in Jira (creating it twice). 

Both issues in Jira show that they have been created by the account we are using to link to Jira (API Owner). We can update the description of one of the issues, and see it reflected in ServiceNow, same of the additional issue: updates the same description.

Does anyone know why ServiceNow would be creating and linking 2 Jira issues to only one ServiceNow Story? 

We have no additional web-hooks configured, only a singular API key connection. 

[Diana_Architect_ZigiWave]

@Matthew Wigglesworth hello. On your question: I think your issue comes from a not properly set integration configuration and the configuration of the field mappings, in particular. Maybe check that out. If you're willing to explore an alternative way of connecting the two systems, take a look at ZigiOps. It helps set the integration instantly and transfer Jira issues and Snow stories. It provides a conditional field mapping for a simplified integration logic. Take a look at it and if you find it interesting, feel free to book a demo to see how exactly it can help connect Jira and ServiceNow without such issues (as the ones you've mentioned).