From 4af992812b5bbd2ab4f1d7efaf9eaf5775946e67 Mon Sep 17 00:00:00 2001 From: "Yann Esposito (Yogsototh)" Date: Wed, 2 Feb 2022 14:50:21 +0100 Subject: [PATCH] notes/remove_securex_tg_login_button.org --- notes/remove_securex_tg_login_button.org | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/notes/remove_securex_tg_login_button.org b/notes/remove_securex_tg_login_button.org index a1249031..7423dd71 100644 --- a/notes/remove_securex_tg_login_button.org +++ b/notes/remove_securex_tg_login_button.org @@ -108,12 +108,13 @@ So to resume - no work to be done on TG side Cons: - probably lot of work on SecureX side (both backend and frontend) as a - comparison it tooks many months for CSA to build this account - migration wofklow. + comparison it took many months for CSA to build this account + migration wofklow and I think there were a lot of UX work and concern before the + development work started. - we still need to propose a login via TG for a long period of time - we will probably force an ultimatum on customer that might open many TAC cases. -2. We could try to use the email (even if they are not verified by TG) +2. We could try to merge account via the email (even if they are not verified by TG) Pros: - Limited work to be done on SecureX side - no work to be done on TG side