Skip to content

Bulk change of incident priority based on category #1151

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

ynr-ram
Copy link
Contributor

@ynr-ram ynr-ram commented Oct 4, 2024

The code helps to automates the bulk update of incident priorities based on predefined category mappings.

ynr-ram added 11 commits October 2, 2022 11:23
This script contains two parts, 1st part is client script and 2nd part is script include.. and this helps to  lock the file till the developer completes his development, so that we can avoid concurrency issues.
Ex: If a "Developer A" working on "Widget A", parallelly if "Developer B" working on "Widget B", then if Developer B moves the code to higher environment before developer A completes his development.. so it creates an issue.. to avoid these kind of concurrency issues.. we can use locking system for each record.. in the above script I shown example for widget records.
Calculate the time difference between incident creation and change implementation
Set due date to incidents based on their priority and the assignment group's working hours
…ty and the assignment group's working hours directory
…creation and related change implementation directory
@snamjosh snamjosh merged commit b5c7278 into ServiceNowDevProgram:main Oct 4, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants