Updating Dashboard to Include Other Status Lookup Values

Updating Dashboard to Include Other Status Lookup Values
DeborahAlbrecht's picture

Have you ever wanted your incidents or your queued incidents (from your team) to reflect a count of Open as well as custom status incidents.

For example, see the screen shot below. This is the Open incidents for myself and for my queue, Application Support. With a little customization to the Dashboard.ascx file I can ensure that this gives me a high level view of not just Open incidents, but incidents on HOLD or incidents with a custom status, such as Update...

Note: Please remember to use all Best Practices for creating customizations on your Helpdesk. For example, all custom files should be placed within a custom folder as to ensure that they are not overwritten during any upgrades or re-installs.

Open your Dashboard.ascx file and find the section below.

<queries>
	<query	id="open"
		type="WorkItem"
		title="sidMyOpenTitle"
		sql="workitem_assigned_to_worker_id = $current_worker_id$ AND (workitem_status_lookup_id = 300 OR workitem_status_lookup_id = 700) " />

	<query	id="queued"
		type="WorkItem"
		title="sidQueuedTitle"
		sql="workitem_status_Lookup_id in (100, 200,  300, 500, 700)" />
	</queries>

As you can see there are 2 sections. One that handles the "open" portion, which is your Open incidents an the other that hands the "queued" incidents.

To update the file and allow the page to show the count including other status incidents, update the SQL to include (for Open) OR workitem_status_lookup_id = xyz, where xyz equals a custom status id number or a built-in status which you would like to add.

For the "queued" section you only need to add a comma and the id number for the status within the parenthesis to including it.

For your convenience, here are the built-in status ids:

100 = Planned

200 = Requested

300 = Open

400 = Resolved

500 = Hold

600 = Closed

700 = custom status value

3.827585
Average: 3.8 (29 votes)

We did this

mboggs's picture

We have already done this, but this article lays it out nicely. Our workers really like this feature because they can view their incidents from any point in the Helpdesk, not just on the Worker Report.

FYI We have seen an increase in deadlocks in the log files since adding this however, but no errors that the workers have experienced on the front end.

Dashboard is very powerful

johnquinn's picture

I have to agree that this is a very nice heads up way to view tickets. When I first implemented it, the management really liked it because it was cusomtized for their group and they could see the tickets at a glance in the queue they managed.

I took it a little further and added other things to watch such as tickets assigned to the New Hire category and even our Hardware Refresh process.

SO the nice thing about this dashboard is it is not restricted to watching just queues. All you need to know is the proper table names and the lookup codes and you can use this to view just about anything.