How do I file a Service, Ticket for meta data or general data updates related to track data, composer updates or publishing requests?

What is required when filing a ticket:

• Ticket Name should be clear and concise
• Ticket Description - can identify the issue but should also be concise.
• Note   - Outlining what is needed and if there are other details needed to communicate the information on what needs to be done.
• Contact - should be the person who is creating the ticket.
• Ticket Owner - is Eddie 
• Pipeline - Defaults to Database Pipeline, also available is a Publishing Pipeline (see below for when to use this pipeline)
• Priority - low, medium and high.  This will be adjusted, as necessary.
• Ticket Status - should be New when creating a new ticket.
• If a ticket already exists for an issue and is closed, un-resolve the ticket, by changing the the ticket status to "Waiting on Us" and add a note to the existing ticket. 
  • A notification will be sent to the ticket owner that the ticket has been reopened.
• Category -  Listed in the below table. Tickets can have multiple categories.
• Source is Internal because we using this feature with our internal team at this point
• Track link should be filled in with the link that needs to attention
• SA link will be filled in with albums lists/playlists (typically for an audit review)

Process:

• Eddie will receive an email every time a new ticket is created so he is aware to check the queue
• Once a resolution is selection and a the Ticket Status is marked to Closed
• An email notification will be sent over to the contact who is associated with the ticket (should be the person who filed the ticket) with an update that the ticket has been closed.
• The contact can review the ticket for any additional information or attachments if necessary.
• Resolution is selected - ticket is closed and closed date is created.
• Issue Resolution - Follow-up is selected a task follow up is created and assigned to the ticket owner

Database Pipeline Categories