User Tools
Writing /app/www/public/data/meta/scotty_pro_ticket_summary.meta failed
scotty_pro_ticket_summary
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| scotty_pro_ticket_summary [2020/07/22 12:48] – 10.91.130.212 | scotty_pro_ticket_summary [2021/06/25 10:09] (current) – created - external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | '' | ||
| + | |||
| + | **Operations Ticket Summary Format.** | ||
| + | |||
| + | New format is: Application Area Action - Issue/ | ||
| + | |||
| + | When it comes to a Topology or Component Discovery issue you only need to mention the technology and software version ( if known ) in the Issue/ | ||
| + | |||
| + | The Support Request Details form has an auto-summary feature which makes filling out tickets easier. | ||
| + | |||
| + | __**Exceptions**__ | ||
| + | |||
| + | __Internal ( Jira ) Application Support Tickets__ | ||
| + | |||
| + | Format: Application/ | ||
| + | |||
| + | The template ticket SUPPORT-1296 can be cloned when creating internal tickets. | ||
| + | |||
| + | Integration tickets would also be opened in this queue, however, they follow their own format. | ||
| + | |||
| + | |||
| + | **__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 on 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 | ||
| + | |||
| + | |||
| + | __**New "Auto Subject" | ||
| + | |||
| + | 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. | ||
| + | * Issue or Request is a free text field to give further details of the ticket. | ||
| + | |||
| + | The auto-subject checkbox when selected will combine the Application, | ||
| + | |||
| + | When the auto-subject checkbox is checked the Groovlet enforces that the summary uses the content of the Area and Action and Issue or Request fields. When you have auto-subject any changes you required to the ticket summary should be done via the drops downs or Issue or Request filed. The running log is still updated when changes are made as it would be if manually edited via ticket info panel. | ||
| + | |||
| + | When creating a ticket via ScottyPro the ticket summary is mandatory so best practice would be to decide the Issue or Request entry here so you can simply copy it into the Issue or Request field when filling out the Support Request Details form. | ||
| + | |||
| + | When you select more than one application the summary will default to start with " | ||
| + | If you are raising a ticket that the auto-summary result isn't suitable you can uncheck the auto-summary checkbox and edit via the ticket info panel. This will ensure that auto-subject Groovlet doesn' | ||
| + | |||
| + | The ticket summary should still follow the correct format as mentioned above. Any feedback on the content of dropdowns should be mentioned to Loughlin, Andrew or Anthony. | ||
| + | |||
| + | The Area and Action field are reading from Database entries so any new changes can be applied to older tickets as long as the ticket has the new version of the Support Request details form. | ||
| + | |||
| + | The monthly tickets are the man exceptions to the ticket summary format in ScottyPro as they have to follow their own format. | ||
Page Tools
