...
Sr. No. | Jira Field | Service Now Field | Jira Field Type | Jira → ServiceNow (Status) | ServiceNow → Jira (Status) | Remark(ServiceNow → JIRA) | Remark(JIRA->ServiceNow) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Summary | Short Description | Text Field (single line) |
|
| Any update to Short Description Field will update the Summary Field in JIRA | |||||||||||||
2 | Description | Description | Text Field (single line) |
|
| Any update to Description Field will update the Description Field in JIRA | |||||||||||||
3 | Comment | Additional comments | WIKI Render |
| |||||||||||||||
4 | Priority | Customer Priority | Text Field (single line) |
| |||||||||||||||
5 | Issue Key | JIRA Issue Key | Text Field (single line) |
| |||||||||||||||
6 | SN Number - CF | Number | Text Field (single line) |
| |||||||||||||||
7 | SN Sys Id - CF | Sys ID | Text Field (single line) |
| |||||||||||||||
8 | Reporter Priority | Customer Priority | Select List (single choice) |
|
| 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 | ||||||||||||
9 | Customer Data Protection | Data Protection Type | Select List (single choice) |
| 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 | |||||||||||||
10 | Environment Type | Used for | Select List (single choice) |
| Working based on the rule sheet | ||||||||||||||
11 | Request Source | Source | Select List (single choice) |
|
| 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 | |||||||||||||
12 | Customer(s) | Customer(s) | Labels |
| |||||||||||||||
13 | Data Center | Prefix Description | Labels |
| Field is disabled for any entry. So, script is not recognizing this field. | Field type is not the same in ServiceNow | |||||||||||||
14 | Affects Version/s | Prefix Description | Labels |
| Field is not visible in ServiceNow, so its not mapped. Note : Script is not recognizing this field. | Field is not available in ServiceNow | |||||||||||||
15 | Component/s | Prefix Description | Labels |
| 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 Description | Request parameters | Endpoint details | Response format | Status | Remark |
---|---|---|---|---|---|---|
1 | List api to get the now fields(Add service now field type to this api) | NA | ||||
2 | List api to get the options for each service now field of the type dropdown | fieldId - service now field id | ||||
3 | List 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 | ||||
4 | Create 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 | ||||
5 | Delete 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 |