---
title: "ServiceNow <> Jira Integration (Legacy)"
canonical: "https://docs.perspectium.com/space/earlierReleases/1442140/ServiceNow%20%3C%3E%20Jira%20Integration%20(Legacy)"
format: markdown
---
This is a legacy feature so it has restricted permissions for Perspectium employees only - it is intended for internal use with customers on a need-by-need basis.  Update Sets To begin integrating SIAM for Jira into your ServiceNow instance, you must first install the Perspectium update sets - request the download links from  support@perspectium.com .  The update sets should be installed in this order: Perspectium for ServiceNow update set Perspectium Common Endpoint Perspectium Common Doc to integrate (ie. Common Incident, Common Change, etc.) Perspectium SIAM for Jira update set Once the update sets have been installed the Perspectium app in the ServiceNow menu will show the  Jira SIAM Integration  tab: Click on  Properties  under the  Jira SIAM Integration tab . Once the page is loaded you should be seeing: In the  Configure the default Jira Project  field enter the Project key value of the Jira Project you wish to share and subscribe to. Make sure that value you enter exactly matches the identifier for the project in Jira. Subscribe Queue If you are planning on subscribing to data from Jira to ServiceNow, you need to set up a subscribe queue. To set up this subscribed queue, you need to know: Name of the queue Endpoint url Queue user Queue user password The endpoint url, queue user, and queue user password will be provided by Perspectium support. The name of the queue is usually in the form psp.out.servicenow.yourinstancename. NOTE:  If you are using two different endpoints for replicator and Jira SIAM, you must set up your Jira SIAM subscribe to use the endpoint url you are using for SIAM. Dynamic Share and Shared Queue After the SIAM base and SIAM for Jira update sets have been installed, a dynamic share and a shared queue should have been created.  To verify that the dynamic share has been created: Click on the  dynamic share  link in the under the  Jira Siam Integration  tab in the Perspectium App. This should open up to a table where an Incident dynamic share should have been created. Click on this dynamic share and verify that the  Active  box is checked, and that under  Additional Settings , the  Table Map  and  Target Queue  fields have values. To verify that the Shared Queue has been created: Click on the  shared queues  link under the  Replicator  tab in the Perspectium App. This should open up a table where a shared queue named psp.in.siam.client.jira should have been created. Click on this Shared Queue and verify that it is active. Stay in this Shared Queues view to complete the Dynamic Share and Shared queue configuration. To complete the configuration you will need: The SIAM endpoint url The Queue user for your SIAM endpoint. The Queue user password for your SIAM endpoint. You will receive the above requirements from Perspectium Support. You will then need to enter this information into the  Endpoint URL ,  Queue user , and  Queue user password  fields in the  psp.in.siam.client.jira  Shared queues. Then,  Update  button in the top right of the shared queue view to save the settings. Creating Dynamic Shares To create your own share for other tables, click the  Dynamic Shares  module under the Perspectium application menu. Click  New  to move on to the dynamic share form. Select the desired table to share and check the  active  box. Then, choose your trigger conditions and move to the  Additional Settings  section of the form. Select the table map that contains Jira and the table name. Select the Target queue  psp.in.siam.client.jira . Make sure to use the code as seen in the image for the  Before share script . This code will make sure any updates, comments, or attachments will be deferred until the record has been ebonded. Here is the code again: if (psp_action == 'update' && current.correlation_id == ''){
	psp_action = 'deferred';
} Outbound and Inbound Table Maps Just like Shared and Dynamic queues, an inbound table map and an outbound table map should have been created after the SIAM update sets were installed. The Inbound table map will handle the conversion of Jira common incidents into ServiceNow incidents. The outbound table map will handle the conversion of ServiceNow Incidents into Jira common incidents. To verify that these have been created: Click the link for the Inbound Maps under the Jira SIAM Integration tab. Verify that Common Incident to Incident for Jira exists in this table. Click the link for the Outbound Maps under the Jira SIAM Integration tab. Verify that Incident to Common Incident (Jira) exists in this table. If either of these maps is missing, please contact   support@perspectium.com