Commit b5c7278
authored
Bulk change of incident priority based on category (#1151)
* Add files via upload
* Create code.js
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.
* Delete code.js
* Delete DisplayTableandFieldNames.js
* Delete readme.md.txt
* Create code.js
Calculate the time difference between incident creation and change implementation
* code.js
Set due date to incidents based on their priority and the assignment group's working hours
* Delete Business Rules/Set due date to incidents based on their priority and the assignment group's working hours directory
* Delete Background Scripts/Calculate time difference between incident creation and related change implementation directory
* Bulk Change of Incident Priority Based on Category.js
* readme.md1 parent f9957be commit b5c7278
File tree
2 files changed
+21
-0
lines changed- Background Scripts/ Bulk Change of Incident Priority Based on Category
2 files changed
+21
-0
lines changedLines changed: 20 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
Lines changed: 1 addition & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
0 commit comments