Skip to content
Home > Posts > Internal request workflows

Internal request workflows

November 9, 2023 |

Internal Workflow New Builds

Leadership:
  • Request through slack channel #wpps-wds-leadership
  • Once approved, on the Parent ticket, mark the field for “Internal” to “Yes”
  • Add the label Internal_Build
Agent:
  • Transition ticket “Setup for build”
Prod:
  • Prod will transition the ticket to “Vendor” to send up the build
  • Note: ALL builds, regardless of internal or not, will generate a Copy Ticket for our Partner Copywriters
Partners:
  • Once the Final copy is written, they will upload the Final copy in the copywriting subtask or Partner ticket
  • Once the copywriting subtask is moved to “Done”, an internal build ticket will be created
Internal:
  • Internal ticket will generate on the Parent ticket (PWS ticket)
  • Builder must grab the final copy from the Partner ticket to proceed with internal build
  • Once completed, move the internal build subtask to “Ready for QA”
QA:
  • QA will review the site and if it’s error-free, they will change the ticket’s status to “Done”, which will send the first draft to the customer.

    • IF QA NEEDS TO SEND TICKET BACK

      QA:
      • If the site contains errors, QA will send them back by changing the ticket’s status to “Needs Edits”
      • QA will leave notes in the Internal Build ticket under “QA/Checklists” labeled as “Design QA Notes” for the edits that need work on
      Internal:
      • Internal team will look at the QA notes for and complete the edits needed
      • Once this is complete, the Internal team will move it back to “Ready for QA”
      QA:
      • QA will complete a re-check, where they will review the site and if the requested tasks are completed, they will change the ticket’s status to “Done” and send the site out to the customer

Internal Workflow Revisions

Leadership:
  • Request through slack channel #wpps-wds-leadership
  • Once approved, on the Parent ticket, mark the field for “Internal” to “Yes”
Agent:
  • Transition ticket to “Revision in Progress”
  • NOTE: If copywriting is selected – this will go to our Partner FIRST before generating a new build subtask

    • IF COPY IS SELECTED “YES”

      Partners:
      • Partner copywriters will work in Copywriting subtask and go over any copy requests
      • When copy is completed, Copywriters will upload the final copy in the copywriting subtask or Partner ticket
      • Once the copywriting task is marked “done”, the internal build ticket will be created
      Internal:
      • Internal ticket will show up on the Parent ticket (PWS ticket)
      • Builder must check if copywriting was being asked for, and grab the final copy from the Partner ticket
      • Once completed, move the internal build subtask to “Ready for QA”
QA:
  • QA will review and if it’s error-free, they will change the ticket’s status to “done”, which will send it to the customer.

    • IF QA NEEDS TO SEND TICKET BACK

      QA:
      • If the site contains errors, QA will send them back by changing the ticket’s status to “Needs Edits”
      • QA will leave notes in the Internal Build ticket under “QA/Checklists” labeled as “Design QA Notes” for the edits that need work on
      Internal:
      • Internal team will look at the notes and complete the edits needed
      • Once this is complete, Internal team will move it back to “Ready for QA”
        QA:
      • QA will complete a re-check, where they will review the site again and if this is completed, they will close out the ticket and send it to the customer
Scroll To Top