User Tools
Writing /app/www/public/data/meta/operations_ticket_summary_format.meta failed
operations_ticket_summary_format
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| operations_ticket_summary_format [2020/10/15 17:06] – 10.91.120.28 | operations_ticket_summary_format [2023/01/28 22:09] (current) – 10.91.110.100 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | '' | ||
| + | '' | ||
| + | |||
| + | |||
| + | __**Operations Ticket Summary Format**__ | ||
| + | |||
| + | The format is: Context - Area Action - Short Details | ||
| + | |||
| + | When it comes to a Topology or Component Discovery issue you only need to mention the technology and software version ( if known ) in the Short Details field. | ||
| + | |||
| + | The Support Request Details form has an auto-summary feature which makes filling out tickets easier.It will update the Summary for you when you save the form. | ||
| + | |||
| + | Please note that the Short Details field shouldn' | ||
| + | |||
| + | |||
| + | |||
| + | **__Why is it important? | ||
| + | |||
| + | |||
| + | •You should get all the important information from the title, this is particularly important on customer calls where the summary is the main focus of a report. | ||
| + | |||
| + | •In the queue or report its easier to spot duplicate tickets | ||
| + | |||
| + | •In the queue or report its easier to spot any trends and take appropriate action | ||
| + | |||
| + | •To maintain consistency | ||
| + | |||
| + | |||
| + | __**" | ||
| + | |||
| + | Three of the new fields on the new Support Request Details form are used to auto-generate the ticket summary these are " | ||
| + | |||
| + | * Area replaces Issue Category and contains a list of areas of the platform to choose from. | ||
| + | * Action contains relevant actions you would take corresponding to each Area. | ||
| + | * Short Details is a free text field to give further details of the ticket. | ||
| + | |||
| + | The Auto Summary Groovlet will combine the Context, Area, Action, and Short Details selections to form the ticket summary when the ticket is saved. | ||
| + | |||
| + | Any changes you require to the ticket summary should be done via the drop-downs or Short Details fields.The running log is still updated when changes are made. | ||
| + | |||
| + | When creating a ticket via ScottyPro the ticket summary is mandatory so the best practice would be to decide on the Short Details entry here so you can simply copy it into the Short Details field when filling out the Support Request Details form. | ||
| + | |||
| + | The fields in The Triage section of the Support Request Details form are prepopulated. You can use the contents of the "Issue Tile" as a guide to what the "Short Details" | ||
| + | |||
| + | When you select more than one item from the context field the summary will default to start with " | ||
| + | If you are raising a ticket that the auto-summary result isn't suitable please contact Loughlin, Anthony or Andrew. | ||
| + | |||
| + | The Area and Action fields are reading from Database entries so any new changes can be applied to older tickets. | ||
| + | |||
| + | Also see [[support: | ||
| + | |||
| + | [[https:// | ||
| + | |||
Page Tools
