:PROPERTIES:
:ID:       97d08dbd-dcab-4776-8450-ff9cdeb7e16b
:END:
#+title: 2021-11-09
* Releasing tagging changes
Releasing the removal of outbound [[id:2ba04972-f498-41c2-970e-a64c7f3f1c3b][Data sanitization]] from the [[id:7e503917-646f-4275-aab9-3a125b99cbfd][Tagging Service]],
addressing the CSLead issue ([[https://jira.aweber.io/browse/CCPANEL-11673][CCPANEL-11673]])that arose from implementing it as a
stopgap as we worked to close the UI sanitization issue.
** CSLead questionairre
The fixes for this issue have been released to production.

- *What was broken? be specific also indicate what was not broken* :: The
  tagging service was temporarily patched to sanitize returned tag labels for
  HTML display, resulting in tags containing sensitive characters to be
  misrepresented (e.g. =this&that= would be returned as =this&ampthat=)
- *When was it broken? start and end date/time* :: Since the tagging service
  started sanitizing returned tag labels on September 9th, 2021.
- *What did you do to fix the problem? be specific* :: A UI sanitization fix was
  propogated to correct the root issue (CCPANEL-11654), and the sanitization was
  removed from the tagging service.
- *How many customers did it likely impact?* :: All customers using tags with
  characters typically escaped as HTML entities (e.g., =<=, =>=, =&=)
- *Is the issue automatically fixed for all customers now? Why or why not?* :: Yes.
  Tags will no longer be misrepresented in autocompletion for searches and
  tagging.
- *Does the customer or CS need to manually do something to fix their account? Customers taking actions should always be a last resort.* :: No.
- *Should a new monitoring check, metric, or test be created to prevent this from happening again? Why or why not?* :: No;
  the system was working as intended.