Translating Client Requests to Tickets

This guide will help you turn client requests into proper edit requests for our design team.

Getting Started

When clients request edits we need to break this down into a list of edits so our designers can be efficient and accurate handling the requests.

When looking at an edit request, mock up, or speaking with the client ask yourself:

• "Where is the edit?"
• "What is the edit?"
• "What is needed to complete the edit?"

Where is the edit?

• What is the page URL?
  • Where on the page is the edit taking place?
  • Header
  • DL
  • Footer
  • Features
  • etc.

When you determine the location of the edit, list that out in the ticket!

Helpful Note: We love screenshot links! Don't be afraid to provide screenshots or an additional reference with Gyazo, CrankWheel, screen grabs, or reference to client provided notes to provide further clarification.

What is the edit?

Determine what kind of edit it is

• Updating
  • change existing text
  • updating existing design
  • switching links
• Adding
  • Adding new gallery page
  • Adding a banner cta
  • Adding a new DL slide
• troubleshooting
  • Not receiving Form submissions
  • Tracking code doesn't work
  • Mobile view looks broken

Once we have an understanding of what we are doing write out the steps in the ticket to achieve the goal.

What is needed to complete the edit?

It's important to interpret what the client needs then restate it and request for the necessary materials! You are the expert here!

• Edit details
  • Client wants it to look like _____
  • This new button needs to link out to ______
  • Clients wants images sorted oldest to newest
  • etc.
• Assets
  • Content that is needed
  • images/videos
  • code

Put it all together

Once we got these three things, we can write them down as edits in the ticket.

Remember to break up the changes to a list of edits (edit 1, edit 2) if we changing multiple things.

Over 8 individual edit requests? Make sure you are submitting in as extensive!