Connecting Neurons for SOM to Jira

perform the following procedures to connect to your jira instance credentials and initial setup log into as an administrator and open the ticket sharing and synchronization (tss) workspace select new ticket sharing and synchronization enter the integration name (example jira) select incident from the business object name menu select enabled from the status menu in the service name field, find and select jira save four new tabs now appear after the credentials tab filters , field mapping , data mapping , and data rules the credentials tab now contains three additional fields a service url relevant jira instance url (example https //customer version atlassian net/rest/api/2) b username jira account username (example jirausername\@company com ) c auth token token provided by jira (example token1232323232323) save filters tab in the filters tab, click new connector service filters in the new connector service filters dialog, select summary from the incident field name menu in the incident field value field, enter trojan operation with next filter determines how filtering works with other filters select the appropriate operator (and or or) (example add a “ransomware detected” filter) when all appropriate filters have been added, save field mapping tab in the field mapping tab, click new connector service field mapping a in the new connector service field mapping dialog, select urgency for the incident field name b enter priority for the jira field name this field is in lowercase in jira c select poll this field for any changes d save click new connector service field mapping a in the new connector service field mapping dialog, select summary for the incident field name b enter summary for the jira field name this field is in lowercase in jira c enter summary for the service field depth d select poll this field for any changes e save click new connector service field mapping a in the new connector service field mapping dialog, select provide default value (to switch field mapping from jira to ism) b enter project for the jira field name c enter esm for the default value d enter project^key for the service field depth e save click new connector service field mapping a in the new connector service field mapping dialog, select description for the incident field name b enter description for the jira field name note this field is in lowercase in jira c enter description for the service field depth d save click new connector service field mapping a in the new connector service field mapping dialog, select status for the incident field name b enter status for the jira field name note this field is in lowercase in jira c select poll this field for any changes d save click new connector service field mapping a in the new connector service field mapping dialog, select provide default value (to switch field mapping from jira to ism) b enter issuetype for the jira field name c enter task for the default value d enter issuetype^name for the service field depth field e save data mapping tab in the data mapping tab, click new connector service data mapping a in the new connector service field mapping dialog, select incident=urgency jira=priority for the connector service field b enter low for the incident field value c enter low for the jira field value d save click new connector service data mapping a select incident=urgency jira=priority for the connector service field b enter low for the incident field value c enter lowest for the jira field value d save click new connector service data mapping a select incident=urgency jira=priority for the connector service field b enter high for the incident field value c enter high for the jira field value d save click new connector service data mapping a select incident=urgency jira=priority for the connector service field b enter high for the incident field value c enter highest for the jira field value d save click new connector service data mapping a select incident=urgency jira=priority for the connector service field b enter medium for the incident field value c enter medium for the jira field value d save click new connector service data mapping a select incident=status jira=status for the connector service field b enter active for the incident field value c enter in progress for the jira field value d save click new connector service data mapping a select incident=status jira=status for the connector service field b enter logged for the field value c enter to do for the jira field value d save click new connector service data mapping a select incident=status jira=status for the connector service field b enter closed for the incident field value c enter done for the jira field value d select stop polling after this value e save data rules tab in the data rules tab, select new connector service field constraint a in the field mapping value menu, select incident=status jira=status\[closed,done] b in the business object field name menu, select causecode c enter hardware for the business object field value d save click new connector service field constraint a in the field mapping value menu, select incident=status jira=status\[closed,done] b in the business object field name menu, select resolution c enter completed for the business object field value d save additional operations click the additional operations tab if the tab is not visible, you may have to refresh or go to list view and select your tss again select the following options push comments added in heat to jira pull comments added in jira to heat push attachments added in heat to jira pull attachments added in jira to heat in the comment business object menu, select journal#notes save comment field mapping click the comment field mapping tab if the tab is not visible, you may have to refresh or go to list view and select your tss again click new comment field mapping a in the incident field name menu, select notes b enter description for the jira field name c save click on new comment field mapping a in the incident field name menu, select source b leave the jira field name blank c enter other for the incident default value d save click on new comment field mapping a in the incident field name menu, select subject b enter summary for the jira field name c save