Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

Table of Contents
stylenone


1. Overview

There shall be a Jira app that can be configured to enable bi-directional sync between Jira and ServiceNow.

...

(This is based on information collected so far. We are still doing requirement analysis with customer).

1.1 Business Requirement

Business needs a plugin for ServiceNow connector for Atlassian Service Desk for seamlessly create/update Issues/Incidents in Jira SD and ServiceNow.

1.2 Pre-requisites

  1. ServiceNow user registration for integration
  2. Local Jira SDK configuration/Installation
  3. Listing the APIs required for ServiceNow integration

2. Proposed Solution

Plugin is intended to provides the facility to create/update incident in ServiceNow . Also, ServiceNow configuration is required to push the incident create/updates to Jira SD.

3. Solution Description


3.1 Features

Sl NoFeatures
1admin user should be able to configure the connection parameters in screen 
2admins user should be able to map the JIRA SD and Service Now Fields
3Any change (create/update/delete/edit) in JIRA SD should update the respective incident in ServiceNow
4Any change (create/update/delete/edit) in ServiceNow should update the respective Task/issues in Jira SD

3.2 User and Roles 

Jira Administrator privileges are required to install/access the plugin.

3.3 Supported Field Type Mapping 

Sr. NoJira Field TypeStatus
1Text Field (single line)
Status
colourGreen
titleDone
2Text Field (multi-line)
Status
colourGreen
titleDone
3Select List (single choice)
Status
colourGreen
titleDone
4WIKI Render
Status
colourGreen
titleDone
5Labels (multi-choice)
Status
colourGreen
titleDone
6Date Picker
Status
titleTODO
7Date Time Picker
Status
colourGreen
titleDone
8Select List (cascading)
Status
titleTODO

3.3 Supported Field Mapping Configuration for SAP Dev Instant

3.4 Supported Field Mapping for SAP Dev Instant

Sr. No.Jira Field Service Now FieldJira Field TypeJira → ServiceNow (Status)ServiceNow → Jira (Status)Remark(ServiceNow → JIRA)Remark(JIRA->ServiceNow)
1SummaryShort DescriptionText Field (single line)
Status
colourGreen
titleDone
Status
colourGreen
titleDone
Any update to Short Description Field will update the Summary Field in JIRA
2DescriptionDescriptionText Field (single line)
Status
colourGreen
titleDone
Status
colourGreen
titleDone
Any update to Description Field will update the Description Field in JIRA
3CommentAdditional commentsWIKI Render
Status
colourGreen
titleDone



4PriorityCustomer PriorityText Field (single line)
Status
colourGreen
titleDone



5Issue KeyJIRA Issue KeyText Field (single line)
Status
colourGreen
titleDone



6SN Number - CFNumberText Field (single line)
Status
colourGreen
titleDone



7SN Sys Id - CFSys IDText Field (single line)
Status
colourGreen
titleDone



8Reporter PriorityCustomer PrioritySelect List (single choice)
Status
colourGreen
titleDone
Status
colourGreen
titleDone

Any update to Customer Priority Field will update the Reporter Priority Field in JIRA.

Note: In Script, we have hard coded the customer field ids and values

Working based on the rule sheet
9Customer Data ProtectionData Protection TypeSelect List (single choice)
Status
colourGreen
titleDone

Any update to Data Protection Type Field will update the Customer Data Protection Field in JIRA.

Note: In Script, we have hard coded the customer field ids and values

Working based on the rule sheet
10Environment TypeUsed forSelect List (single choice)
Status
colourGreen
titleDone


Working based on the rule sheet
11Request SourceSourceSelect List (single choice)
Status
colourGreen
titleDone
Status
colourGreen
titleDone

Any update to Source Field will update the Request Source Field in JIRA.

Note: In Script, we have hard coded the customer field ids and values


12Customer(s)Customer(s)Labels
Status
colourGreen
titleDone



13Data CenterPrefix DescriptionLabels
Status
colourGreen
titleDone

Field is disabled for any entry. So, script is not recognizing this field.Field type is not the same in ServiceNow
14Affects Version/sPrefix DescriptionLabels
Status
colourGreen
titleDone

Field is not visible in ServiceNow, so its not mapped.

Note : Script is not recognizing this field.

Field  is not available in ServiceNow
15Component/sPrefix DescriptionLabels
Status
colourGreen
titleDone

Field is not visible in ServiceNow, so its not mapped.

Note : Script is not recognizing this field.

Field is not available in ServiceNow


3.4 API details for mapping between Jira field options and Service now field options

Sr. No.API DescriptionRequest parametersEndpoint detailsResponse formatStatusRemark
1List api to get the now fields(Add service now field type to this api) NA



2List api to get the options for each service now field of the type dropdown

fieldId - service now field id





3List api to get list of all the mappings between Jira field options and service now field options

projectKey - key of the project

issueType - issue type related to the project

jiraFieldId - id of the Jira field

serviceNowFieldId - id of the service now field





4Create api to add mapping between the Jira field option and Service Now field option

projectKey - key of the project

issueType - issue type related to the project

jiraFieldId - id of the Jira field

serviceNowFieldId - id of the service now field

jiraOptionId - id of the Jira option pertaining to Jira field

serviceNowOptionId - Id of the service now option pertaining to service now field





5Delete api endpoint to delete data for the mapping between Jira field option and Service Now field option

projectKey - key of the project

issueType - issue type related to the project

jiraFieldId - id of the Jira field

serviceNowFieldId - id of the service now field

jiraOptionId - id of the Jira option pertaining to Jira field

serviceNowOptionId - Id of the service now option pertaining to service now field





6Get transition API Issue Keyhttp://empyratestqa.eastus.cloudapp.azure.com/rest/api/2/issue/COSD-4/transitions

It gives all possible transaction for the issues  
7Post  transition API


Code Block
{
    "update": {
        "comment": [
            {
                "add": {
                    "body": "Comment added when resolving issue"
                }
            }
        ]
    },
    "transition": {
        "id": "2"
    }
}


http://empyratestqa.eastus.cloudapp.azure.com/rest/api/2/issue/COSD-4/transitions

It updates transaction.

Reference to update other fields with transition 

https://docs.atlassian.com/software/jira/docs/api/REST/8.5.4/#api/2/issue-doTransition 

8Post attachments 


Code Block
 Header: 
Authorization: Basic c3Zpc2h3YWthcm1hOnN2aXNod2FrYXJtYQ==
X-Atlassian-Token: no-check
Content-Type: multipart/form-data; 

form-data:

name="file"; filename="Assig.PNG"
Content-Type: image/png




http://empyratestqa.eastus.cloudapp.azure.com/rest/api/2/issue/COSD-4/attachments

It creates an attachment for the JIRA issue.