Devops : Parent field values are not updated for work items imported from JiraIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Create an Epic, for example LTR-71, and link the child Stories, for example LTR-72, LTR-73, LTR-164. When importing into ServiceNow, these Stories are not associated with the Epic; their parent field is empty. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The issue is likely to occur if the value for the parent field sent by Jira is not mapped to the default fields updated in the ServiceNow scripting components. For example, In this case, the parent field value was passed by Jira in the custom field 'customfield_10008' as shown below. However, the script include 'sn_devops.DevOpsPlanFieldMapping' has the field mapping defined only to process and update the payload if the parent field value is sent in one of the following fields: 'customfield_10101' and 'customfield_10102', causing parent details to remain empty during import. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } 1. Update the 'epic_custom_field_id' in the script include 'sn_devops.DevOpsPlanFieldMapping' to include 'customfield_10008' instead of 'customfield_10101' and 'customfield_10102'. ↳ EX: To resolve the issue based on the values shared in Jira for the above example, replace the following in the script include: sn_devops.DevOpsPlanFieldMapping # Link to the script include Note: Use the appropriate custom fields for mapping that share the parent details based on your Jira setup.Current value:jira: {map_to_plan: 'project',map_to_feature: 'epic',map_to_version: 'release',map_to_work_item: 'issue',epic_custom_field_id: ['customfield_10101', 'customfield_10102']}New values jira: {map_to_plan: 'project',map_to_feature: 'epic',map_to_version: 'release',map_to_work_item: 'issue',epic_custom_field_id: ['customfield_10008']} 2. Reimport the work items from the corresponding plan configured in the instance3. Verify the parent field values in the imported work items to ensure they are correctly populated. NOTE: It is also important to verify that the parent Epic record exists in ServiceNow before creating and sending child stories from Jira.