You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

See also

Goal

Identify all resolved tickets in time-period.

Process

I wrote to Frank 1/14/16 to request report from Greg Christofferson. Excerpt:

Thanks for discussing Remedy reports with me this morning, inspired by Greg Christofferson’s <gc88> recent referral to me. Greg thought he was already sending you the report data that I had discussed with him I wanted for our group.

What you and I discussed is if we could start with getting data for one month, to start. Get data for each of the 4 full-time staff members in Chemistry IT/ Physics IT with how many tickets we resolved in the Chemistry queue. Once we nail down a report with the right info we can broaden the time, include student staff, and pull in data from our other 2 queues (Chemistry 2 and Physics).

Details

This provides us with a measure of volume, to compare with our monthly snap-shots of outstanding tickets.

Process idea: Do for each month (or quarter), starting with the past 6 months (or 2 years).

Implementation ideas

Example 1: Spreadsheet

In the Month of Sept 2015, ChemIT (Assigned groups: Chemistry and Chemistry (L2)) and PhysIT (Assigned group: Physics) resolved x number of tickets. The are as follows (in a spreadsheet):

Assigned Group, Summary, First Name, Last Name, Contact Type, Reported Date (Why are there two? Do they differ?), Responded Date, Last Resolved Date, Closed Date, Last Acknowledged Date, Last Modified, Re-Opened Date, Service, Status (is either resolved or (auto-)closed, depending on query date), Assignee, Resolution, Customer Building Name, ID.

Example 2: Pie charts

Pie chart for ChemIT and separate pie chart for PhysIT showing tickets completed by staff member. Annual snapshot?

  • Similar to the Library's Desktop Services "DS Resolved Incidents 2014" and "DS Resolved Incidents 2015" web reports.

 

 

 

 

 

  • No labels