From db61544510bad073adb735e6b52b30c652c7a73b Mon Sep 17 00:00:00 2001 From: DGAJ <112356379+D-GAJ@users.noreply.github.com> Date: Mon, 6 Oct 2025 19:49:22 +0100 Subject: [PATCH 01/11] Create Readme.md --- .../Readme.md | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 Server-Side Components/Business Rules/Reset Change model workflow when model changes/Readme.md diff --git a/Server-Side Components/Business Rules/Reset Change model workflow when model changes/Readme.md b/Server-Side Components/Business Rules/Reset Change model workflow when model changes/Readme.md new file mode 100644 index 0000000000..18a16c6e72 --- /dev/null +++ b/Server-Side Components/Business Rules/Reset Change model workflow when model changes/Readme.md @@ -0,0 +1,6 @@ +#contribution +This Business Rule will reset previous workflow changes, when the model field on a change record changes to a different model. +Table - Change Request (change_request) +Advanced set to True +When to Run - Before Update +Filter Conditions: Model changes From 37dc36771525cef47808b7b29c90f4098e3e7489 Mon Sep 17 00:00:00 2001 From: DGAJ <112356379+D-GAJ@users.noreply.github.com> Date: Mon, 6 Oct 2025 19:54:39 +0100 Subject: [PATCH 02/11] Create code.js --- .../code.js | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 Server-Side Components/Business Rules/Reset Change model workflow when model changes/code.js diff --git a/Server-Side Components/Business Rules/Reset Change model workflow when model changes/code.js b/Server-Side Components/Business Rules/Reset Change model workflow when model changes/code.js new file mode 100644 index 0000000000..5cad0bfab3 --- /dev/null +++ b/Server-Side Components/Business Rules/Reset Change model workflow when model changes/code.js @@ -0,0 +1,10 @@ +//This Business rule will reset a change workflow ,when the change model changes +(function executeRule(current, previous /*null when async*/) { + + // Create a new instance of the Workflow class + var wkfw = new Workflow(); + + // Delete the workflow associated with the current record + wkfw.deleteWorkflow(current); + +})(current, previous); From 73678a4f4222243a732f7abcd88bcb9ad600de60 Mon Sep 17 00:00:00 2001 From: DGAJ <112356379+D-GAJ@users.noreply.github.com> Date: Tue, 21 Oct 2025 23:02:56 +0100 Subject: [PATCH 03/11] Create Convert Incident to a story --- Client-Side Components/UI Actions/Convert Incident to a story | 1 + 1 file changed, 1 insertion(+) create mode 100644 Client-Side Components/UI Actions/Convert Incident to a story diff --git a/Client-Side Components/UI Actions/Convert Incident to a story b/Client-Side Components/UI Actions/Convert Incident to a story new file mode 100644 index 0000000000..8b13789179 --- /dev/null +++ b/Client-Side Components/UI Actions/Convert Incident to a story @@ -0,0 +1 @@ + From 0a3f900c54180377d7f6cb8576a2656cc5dcf342 Mon Sep 17 00:00:00 2001 From: DGAJ <112356379+D-GAJ@users.noreply.github.com> Date: Tue, 21 Oct 2025 23:04:53 +0100 Subject: [PATCH 04/11] Delete Client-Side Components/UI Actions/Convert Incident to a story --- Client-Side Components/UI Actions/Convert Incident to a story | 1 - 1 file changed, 1 deletion(-) delete mode 100644 Client-Side Components/UI Actions/Convert Incident to a story diff --git a/Client-Side Components/UI Actions/Convert Incident to a story b/Client-Side Components/UI Actions/Convert Incident to a story deleted file mode 100644 index 8b13789179..0000000000 --- a/Client-Side Components/UI Actions/Convert Incident to a story +++ /dev/null @@ -1 +0,0 @@ - From f9c6dd1a5464f879d34d65cac0b5ad6aef7d7891 Mon Sep 17 00:00:00 2001 From: DGAJ <112356379+D-GAJ@users.noreply.github.com> Date: Tue, 21 Oct 2025 23:41:59 +0100 Subject: [PATCH 05/11] Create Convert Incident to a story Incident-to-Story Conversion UI Action As a ServiceNow admin, I want to be able to convert cidents or Tasks into Development Stories with a single UI action so that operational issues can be seamlessly ansitioned into Agile work items for remediation and platform improvement. --- Client-Side Components/UI Actions/Convert Incident to a story | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 Client-Side Components/UI Actions/Convert Incident to a story diff --git a/Client-Side Components/UI Actions/Convert Incident to a story b/Client-Side Components/UI Actions/Convert Incident to a story new file mode 100644 index 0000000000..87522396ae --- /dev/null +++ b/Client-Side Components/UI Actions/Convert Incident to a story @@ -0,0 +1,4 @@ +# Incident-to-Story Conversion UI Action + +As a ServiceNow admin, I want to be able to convert cidents or Tasks into Development Stories with a single UI action so that operational issues +can be seamlessly ansitioned into Agile work items for remediation and platform improvement. From aedb92ac6b4b30c94d5d1ec6f656157e8520c6e9 Mon Sep 17 00:00:00 2001 From: DGAJ <112356379+D-GAJ@users.noreply.github.com> Date: Tue, 21 Oct 2025 23:45:27 +0100 Subject: [PATCH 06/11] Delete Client-Side Components/UI Actions/Convert Incident to a story --- Client-Side Components/UI Actions/Convert Incident to a story | 4 ---- 1 file changed, 4 deletions(-) delete mode 100644 Client-Side Components/UI Actions/Convert Incident to a story diff --git a/Client-Side Components/UI Actions/Convert Incident to a story b/Client-Side Components/UI Actions/Convert Incident to a story deleted file mode 100644 index 87522396ae..0000000000 --- a/Client-Side Components/UI Actions/Convert Incident to a story +++ /dev/null @@ -1,4 +0,0 @@ -# Incident-to-Story Conversion UI Action - -As a ServiceNow admin, I want to be able to convert cidents or Tasks into Development Stories with a single UI action so that operational issues -can be seamlessly ansitioned into Agile work items for remediation and platform improvement. From 450361e770a8a31a8ca73afff46696047b519e7a Mon Sep 17 00:00:00 2001 From: DGAJ <112356379+D-GAJ@users.noreply.github.com> Date: Tue, 21 Oct 2025 23:56:25 +0100 Subject: [PATCH 07/11] Create ReadMe.md Incident-to-Story Conversion UI Action As a ServiceNow admin, I want to be able to convert incidents into Development Stories with a single UI action so that operational issues can be seamlessly transitioned into Agile work items for remediation and platform improvement. Original incident can be closed with story number as a reference for the user. Very helpful if incident requires development effort. --- .../UI Actions/Convert Incident to a story/ReadMe.md | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 Client-Side Components/UI Actions/Convert Incident to a story/ReadMe.md diff --git a/Client-Side Components/UI Actions/Convert Incident to a story/ReadMe.md b/Client-Side Components/UI Actions/Convert Incident to a story/ReadMe.md new file mode 100644 index 0000000000..665e725dad --- /dev/null +++ b/Client-Side Components/UI Actions/Convert Incident to a story/ReadMe.md @@ -0,0 +1,9 @@ +Incident-to-Story Conversion UI Action + +As a ServiceNow admin, I want to be able to convert incidents into Development Stories with a single UI action so that operational issues +can be seamlessly transitioned into Agile work items for remediation and platform improvement. +Original incident can be closed with story number as a reference for the user. + +Very helpful if incident requires development effort. + +image From 4b30e3640b8d18b6ac41d832eb10cf325126f3a1 Mon Sep 17 00:00:00 2001 From: DGAJ <112356379+D-GAJ@users.noreply.github.com> Date: Wed, 22 Oct 2025 00:02:28 +0100 Subject: [PATCH 08/11] Create code.js UI action script --- .../Convert Incident to a story/code.js | 32 +++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 Client-Side Components/UI Actions/Convert Incident to a story/code.js diff --git a/Client-Side Components/UI Actions/Convert Incident to a story/code.js b/Client-Side Components/UI Actions/Convert Incident to a story/code.js new file mode 100644 index 0000000000..59309be409 --- /dev/null +++ b/Client-Side Components/UI Actions/Convert Incident to a story/code.js @@ -0,0 +1,32 @@ +// Get caller ID from the incident record +var callerID = current.caller.id; + +// Initialize new story record +var gr = new GlideRecord("rm_story"); +gr.short_description = current.short_description; // Copy short description +gr.description = current.description; // Copy full description +gr.type = "Fix"; // Set story type to 'Fix' + +// Assign caller as both requirements owner and tester +gr.u_tester = current.caller_id; + +// Link story to originating incident +gr.u_created_from = current.sys_id; //cutom field to populate incident record or request -not required + +// Insert story and capture its sys_id +var sysID = gr.insert(); + +// Store story sys_id on incident for traceability +current.rm_story_id = sysID; + +// Update incident record +var mySysID = current.update(); + +// Display confirmation message with story number +gs.addInfoMessage("Agile Story " + gr.number + " created"); + +// Redirect user to newly created story +action.setRedirectURL(gr); + +// Set return URL to original incident +action.setReturnURL(current); From cfaf0553ddca994e3caebaf7617e2a5462b3dca2 Mon Sep 17 00:00:00 2001 From: DGAJ <112356379+D-GAJ@users.noreply.github.com> Date: Wed, 22 Oct 2025 00:21:40 +0100 Subject: [PATCH 09/11] Create Readme.md Catalog task(sc_task)-to-Story Conversion UI Action As a ServiceNow admin, I want to be able to convert catalog task into Development Stories with a single UI action so that operational issues can be seamlessly transitioned into Agile work items for remediation and platform improvement. Very helpful if requests requires development effort. --- .../UI Actions/Convert Catalog Task to a story/Readme.md | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 Client-Side Components/UI Actions/Convert Catalog Task to a story/Readme.md diff --git a/Client-Side Components/UI Actions/Convert Catalog Task to a story/Readme.md b/Client-Side Components/UI Actions/Convert Catalog Task to a story/Readme.md new file mode 100644 index 0000000000..72bdf107a6 --- /dev/null +++ b/Client-Side Components/UI Actions/Convert Catalog Task to a story/Readme.md @@ -0,0 +1,6 @@ +Catalog task(sc_task)-to-Story Conversion UI Action + +As a ServiceNow admin, I want to be able to convert catalog task into Development Stories with a single UI action so that operational issues can be seamlessly transitioned into Agile work items for remediation and platform improvement. +Very helpful if requests requires development effort. + +image From d91098a3b4265af504731e394e9e704577fbc746 Mon Sep 17 00:00:00 2001 From: DGAJ <112356379+D-GAJ@users.noreply.github.com> Date: Wed, 22 Oct 2025 00:24:33 +0100 Subject: [PATCH 10/11] Create script.js UI action script code --- .../Convert Catalog Task to a story/script.js | 32 +++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 Client-Side Components/UI Actions/Convert Catalog Task to a story/script.js diff --git a/Client-Side Components/UI Actions/Convert Catalog Task to a story/script.js b/Client-Side Components/UI Actions/Convert Catalog Task to a story/script.js new file mode 100644 index 0000000000..3f69112621 --- /dev/null +++ b/Client-Side Components/UI Actions/Convert Catalog Task to a story/script.js @@ -0,0 +1,32 @@ +// Initialize new GlideRecord for rm_story table +var gr = new GlideRecord("rm_story"); + +// Copy description from current record (likely a Requested Item or similar) +gr.description = current.description; + +// Set story type to 'Enhancement' +gr.type = "Enhancement"; + +// Assign requested_for user as tester +gr.u_tester = current.request.requested_for; //custom field-optional + +// Link story to source record via u_created_from field +gr.u_created_from = current.sys_id; //optional custom field to link request to story + +// Insert the new story and capture its sys_id +var sysID = gr.insert(); + +// Store the story sys_id in the source record for traceability +current.rm_story_id = sysID; + +// Update the source record +var mySysID = current.update(); + +// Display confirmation message with story number +gs.addInfoMessage("Agile Story " + gr.number + " created"); + +// Redirect user to the newly created story +action.setRedirectURL(gr); + +// Set return URL to the original source record +action.setReturnURL(current); From 34834c49c3491f59b912ddcce3e589940a48ad9d Mon Sep 17 00:00:00 2001 From: DGAJ <112356379+D-GAJ@users.noreply.github.com> Date: Wed, 22 Oct 2025 00:25:39 +0100 Subject: [PATCH 11/11] Update code.js UI action script code --- .../UI Actions/Convert Incident to a story/code.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Client-Side Components/UI Actions/Convert Incident to a story/code.js b/Client-Side Components/UI Actions/Convert Incident to a story/code.js index 59309be409..71cf35b2a7 100644 --- a/Client-Side Components/UI Actions/Convert Incident to a story/code.js +++ b/Client-Side Components/UI Actions/Convert Incident to a story/code.js @@ -7,7 +7,7 @@ gr.short_description = current.short_description; // Copy short description gr.description = current.description; // Copy full description gr.type = "Fix"; // Set story type to 'Fix' -// Assign caller as both requirements owner and tester +// Assign caller as tester gr.u_tester = current.caller_id; // Link story to originating incident