====== Errigal Support Reports ====== Author: Michelle McCausland
Updated: Loughlin Moore
NOTE: Report is now automated, I will add details on how to run report soon. The below information is no longer applicable
===== Introduction ===== The Errigal support reports, or internal support reports, are used to provide an overview of the active tickets from the previous week eg. tickets opened, tickets closed, ticket aging, total backlog etc. NOTE: Please consult with Paddy/Robert for more detail on this process as new changes may have occurred. These reports are generated on Monday morning and are distributed to the team. Screenshots of these charts are added to the information radiator here : Information Radiator. Previous examples of this can be found in the following email chains: Support Graph - 28th Aug (just change the date accordingly). —- ===== Steps ===== 1. To begin, take a copy of the report from the previous week and rename to be the current date. Ideally they should be stored in a separate “Support Reports” folder. 2. The first tab is Crown. In the Date column, add the next set of dates - you want the previous week of data so use the previous dates to guide you. Report Columns: * Opened / Closed - The number of tickets opened and closed for that week period. (Can be retrieved in Jira for Crown and Errigal, retrieved in the Scotty Pro Reporting Manager for Extenet). * Avg Closed Ticket Aging - This provides an average of the time to close the tickets closed in the last week (See below for more detail). * Total - This should be a formula value which sums up the following state values. (Copy and paste the value above to get the formula). * Open / In Progress / On Hold / Response Provided / Awaiting Response - Each of these columns should contain the number of tickets in each of these states (Awaiting response includes pending approval items for now for Crown Castle). Avg Closed Ticket Aging Jira - Export the jira search for tickets closed in the last week and ensure create date and resolved date are included. To calculate the ticket aging: subtract resolved from created for each row and then find the average. Scotty Pro - Export “Extenet tickets closed in the last week”. To calculate the ticket aging: subtract resolved from created for each row and then find the average. 3. With the numbers completed, it is necessary to update the chart to the right of the stats. Click on an area of whitespace on the chart, now move the selected data selection so that the correct values are represented on the chart (Just move the selection 1 row down). You should then see the chart update. 4. Take a screenshot of the CC graph for use on the information radiator and for the weekly. 5. Follow the same process for the Extenet & Errigal tabs, ensuring to take screenshots of the graphs. 6. The totals tab provides an overview of the total tickets opened v closed. As before, add the correct date range, add the data and update the charts. No need to update the bottom 2 charts. 7. Once the file has been updated, it is time to send it out. Refer back to the previous week's email to get the email template format: <code>Hi all, I have updated the support graphs with last weeks stats: CC Total backlog at end of week: 20 Tickets Opened: 1 Tickets Closed: 4 EXT Total backlog at end of week: 47 Tickets Opened: 2 Tickets Closed: 1 ERR Total backlog at end of week: 88 Tickets Opened: 3 Tickets Closed: 6 Please let me know if you need anything else. Kind Regards,</code> Send the email to the distribution from the previous email, this is always the same. —- ===== Update the Information Radiator =====