Processes Home

New Build – Workflow

Published On: March 29, 2022/Last Updated August 16, 2023

Under no circumstances should Builders email or communicate directly with customers.
Please rely on our Website Specialists to communicate with our customers.

  1. Middle click (Open in a new tab) the second link in the summary tab ending in “- Build”.
  2. At the top of the page click on the dropdown that says “Ready” and choose “In Progress”.
  1. Leave an internal comment indicating you have begun work.
  2. Once all possible work has been completed, make sure you QA your work (http://wdsdesigns.com/qa-check/) before sending the ticket to QA to avoid unnecessary Edits. Make sure to notate any items that you were unable to address and why.
  3. Click on the “In Progress” dropdown and choose “Send for QA”.
  4. Make sure your Site Preview Link includes the whole URL (including the http://). This will be helpful in the future since it updates the link on Jira.
  5. Leave any notes you have in the Builder Clarifications section on the pop up, and it is good practice to copy and paste the notes to internal comments.  
  6. Click the “Send For QA” button.
Technical Clarification

Do not send for non technical clarifications. They will not go to anyone and get lost in the Matrix

Builders are expected to be skilled in technical troubleshooting for our websites, software, plugins, and applications. Do not hesitate to reach out to your team and leadership to find solutions to technical issues first.

  1. If the ticket needs to go to a Builder 3 for technical troubleshooting, such as Beaver Builder not loading, Click the “In Progress” dropdown and choose “Clarification Needed” 
  2. Select the “Yes” option in the Technical Clarification dropdown. This will send the tickets to our internal Builder 3’s to troubleshoot.
  3. Using the Panel Template, leave notes in the ticket about the issues you have encountered.
  4. After you have left your notes, click on the “Clarification Needed” button.
  5. Once the clarification has been completed on the Builder 3 side, it will come back into our bucket for New Care Tickets.
    • Note: It does not auto assign to the last builder. If you see a ticket come in that you requested a clarification for please grab it, as you probably know more about the ticket than a new person picking it up.
  6. Click the “Ready” dropdown and choose “In Progress”, leave your note indicating your working on the ticket, then once you have completed everything click the dropdown at the top that says “In Progress” and choose “Design Complete – Send for QA” leaving any notes you may have, including a completion note.
Needs Edits
  1. If the ticket has been returned to you from the QA team as needs edits, start by clicking on the “Apply Edits” button at the top.
  2. Notate that you are starting work.
  3. After the work has been completed, leave notes about what you did or did not do and why.
  4. Include a completion note.
  5. Then click the “Send For QA” button at the top.
  6. Once more on the pop up, if you have any notes to add the build ticket, add them here and click the “Send For QA” button once more. 

Panel Template

Please adjust the title and notes accordingly.

{panel:title=Technical Clarification 1 - Critical Error}

*All tasks completed except:*

*Page:* Home
*Instruction:* Add content from 3 pages on the live site onto the home page
*Issue:* Can't load page and getting a critical error on the home page only
*Steps taken to troubleshoot:*

* troubleshooting step 1 – updated plugins
* troubleshooting step 2 – uploaded .user.ini file
* troubleshooting step 3 – cleared cache from GD cORe dropdown.

{panel}