Skip to content

Active tickets dashboard in service portal #1147

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

Overview
The Active Tickets Dashboard Widget displays a summary of active incidents, changes, problems, and catalog tasks assigned to the logged-in user. This widget provides a quick overview of the user's current workload, enhancing efficiency in managing tasks.

Features
Displays counts for:

  1. Active Incidents
  2. Active Changes
  3. Active Problems
  4. Active Catalog Tasks

Each tile is clickable, leading to a filtered list of records based on the logged-in user.

Setup Instructions

  1. Create a New Widget
  2. Navigate to Service Portal > Widgets in the ServiceNow application navigator.
  3. Click on New to create a new widget.
  4. Fill in the Name (e.g., "Active Tickets Dashboard") and select a suitable Widget Type (e.g., "Custom") and copy paste all the code into the releavant sections.

Usage
After setting up the widget, add it to the desired Service Portal page.

The widget will display the counts of active incidents, changes, problems, and catalog tasks assigned to the logged-in user.

Clicking on any tile will navigate the user to the corresponding list view with the applied filters.

ynr-ram added 17 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
@ashu759 ashu759 self-assigned this Oct 4, 2024
Copy link
Contributor

@ashu759 ashu759 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks Good.

@ashu759 ashu759 merged commit 115e379 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