Prodcast: Legacy Platforms
In this video, we’re going to talk about something that you’ve most likely encountered as WS1’s, and that’s creating and submitting a Post Publish ticket for a legacy website.
The Video
The Why
First things first: It’s important to know which platforms are considered legacy platforms and which ones are not.
You’ve probably seen some of the old GoDaddy propriety platforms like Website Builder v7 and Online Store. You may have also seen Quick Shopping Cart, which we have very few left of and even Website Builder v6, which has been discontinued and should no longer exist anywhere.
The only two platforms that are not considered legacies are WordPress-any plan types, including starters, and Websites+Marketing.
One thing to understand is that opening a legacy platform ticket is not the same as opening a standard post publish ticket. They are not the same. This seems to be a sticking point, especially with the newer website specialists. These two tickets are treated completely differently, so you need to make sure you’re submitting the correct ticket.
All legacy tickets are done internally. The reason for this is because the only way to access them is by getting into the customer account, which only someone with access to our internal servers can do, like an internal builder.
However, WordPress and Websites+Marketing can be accessed from an external source, so those will always be sent externally to our vendors.
The How
So when you’ve established that the customer is on an older GoDaddy platform and not on WordPress or Websites+Marketing, follow the Confluence article instructions for submitting a Legacy Updates Request which will look like this.
If you need to submit a post publish ticket and the customer is on a WordPress or Websites+Marketing website, follow the Confluence article instructions for submitting a post publish ticket which will start off by looking like this.
So always remember—WordPress and W+M are not legacy platforms, so a post publish ticket and not a legacy update request needs to be submitted.
They are different processes, so make sure you’re submitting the correct ticket to avoid any delays and escalated customers.
As always if you have questions, you can lean on teammates, your Team Lead/Team Manager, LOTD and BOTD, and now POTD. Thanks again for watching, and stay tuned for another episode of the Prodcast!
Opening a Legacy Update Ticket in Jira
How to find out if our Legacy customer has “updates” included in their hosting plan