This commit is contained in:
Correl Roush 2022-03-10 23:27:57 -05:00
parent 7c3fad8cfb
commit 084fd80e1d
4 changed files with 63 additions and 26 deletions

View file

@ -19,6 +19,6 @@ efforts:
The CakePHP Control Panel application will be replaced with a modern alternative
handling routing and React application loading.
* Overhauling logins and session management
* [[id:0328a202-376d-4e97-b0e3-031eaad2a557][Overhauling logins and session management]]
The session-based login mechanism of the legacy Control Panel application is to
be replaced with OAuth, which is used for public API requests.

View file

@ -27,39 +27,44 @@ visualized.
:COLUMNS: %50ITEM %JIRA_ID %Effort{:}
:END:
#+BEGIN: columnview
| ITEM | JIRA_ID | Effort |
|-----------------------------------------------------------------------------------+---------------+----------|
| Roll-out | | 19d 0:00 |
| Normalize when comparing tags | | 4d 4:00 |
| Update Campaign Engine to apply normalization rules when comparing tags | CCPANEL-12031 | 1.5d |
| Update Analytics DB Search Terms to apply normalization rules when comparing tags | | 3d |
| Normalize incoming data | CCPANEL-12009 | 5d 0:00 |
| Update [[id:7e503917-646f-4275-aab9-3a125b99cbfd][Tagging Service]] to normalize tags | CCPANEL-12010 | 2d |
| Update [[id:aa9b1fdc-d766-41bb-ab7b-11c35bca54fa][AWSubscribers]] to normalize tags | CCPANEL-12011 | 2d |
| Update TagBox to normalize tags | | |
| Normalize tags when storing in rule sets | | 1d |
| Normalize existing tag data | CCPANEL-12013 | 8d 0:00 |
| Update tags in rulesets to conform to normalization rules | CCPANEL-12014 | 3d |
| Update tags in segments to conform to normalization rules | CCPANEL-12015 | 3d |
| Update tags in the tagging database to conform to normalization rules | CCPANEL-12016 | 2d |
| Remove comparison normalization logic | | 1d 4:00 |
| Remove normalized comparisons from Campaign Engine | | 4h |
| Remove normalized comparisons from Analytics DB Search Terms | | 1d |
| Normalize externally stored tags | | |
| Normalize tags when storing in Stripe | | |
| Integrations | | |
#+BEGIN: columnview :indent t
| ITEM | JIRA_ID | Effort |
|-----------------------------------------------------------------------------------------+---------------+----------|
| Roll-out | | 21d 0:00 |
| \_ Normalize when comparing tags | CCPANEL-12033 | 4d 4:00 |
| \_ Update Campaign Engine to apply normalization rules when comparing tags | CCPANEL-12031 | 1.5d |
| \_ Update Analytics Search DB Terms to apply normalization rules when comparing tags | CCPANEL-12034 | 3d |
| \_ Normalize incoming data | CCPANEL-12009 | 5d 0:00 |
| \_ Update [[id:7e503917-646f-4275-aab9-3a125b99cbfd][Tagging Service]] to normalize tags | CCPANEL-12010 | 2d |
| \_ Update [[id:aa9b1fdc-d766-41bb-ab7b-11c35bca54fa][AWSubscribers]] to normalize tags | CCPANEL-12011 | 2d |
| \_ Update TagBox to normalize tags | CCPANEL-12035 | |
| \_ Normalize tags when storing in rule sets | CCPANEL-12036 | 1d |
| \_ Normalize existing tag data | CCPANEL-12013 | 10d 0:00 |
| \_ Update tags in rulesets to conform to normalization rules | CCPANEL-12014 | 3d |
| \_ Update tags in segments to conform to normalization rules | CCPANEL-12015 | 3d |
| \_ Update tags in the tagging database to conform to normalization rules | CCPANEL-12016 | 2d |
| \_ Update tags in the subscriber tags table to conform to normalization rules | CCPANEL-12037 | 2d |
| \_ Remove comparison normalization logic | CCPANEL-12038 | 1d 4:00 |
| \_ Remove normalized comparisons from Campaign Engine | CCPANEL-12039 | 4h |
| \_ Remove normalized comparisons from Analytics DB Search Terms | CCPANEL-12040 | 1d |
| \_ Normalize tags stored outside of tagging and campaigns | CCPANEL-12041 | |
| \_ Normalize tags when storing in Stripe | | |
| \_ Integrations | | |
#+END:
** Normalize when comparing tags
:PROPERTIES:
:JIRA_ID: CCPANEL-12033
:END:
*** Update Campaign Engine to apply normalization rules when comparing tags
:PROPERTIES:
:JIRA_ID: CCPANEL-12031
:EFFORT: 1.5d
:END:
*** Update Analytics DB Search Terms to apply normalization rules when comparing tags
*** Update Analytics Search DB Terms to apply normalization rules when comparing tags
:PROPERTIES:
:EFFORT: 3d
:JIRA_ID: CCPANEL-12034
:END:
** Normalize incoming data
:PROPERTIES:
@ -76,17 +81,21 @@ visualized.
:JIRA_ID: CCPANEL-12011
:END:
*** Update TagBox to normalize tags
:PROPERTIES:
:JIRA_ID: CCPANEL-12035
:END:
- Needs UX
- Should this also change the display of non-normalized tags?
*** Normalize tags when storing in rule sets
:PROPERTIES:
:EFFORT: 1d
:JIRA_ID: CCPANEL-12036
:END:
Campaign proxy / rule service
** Normalize existing tag data
:PROPERTIES:
:JIRA_ID: CCPANEL-12013
:EFFORT: 8d 0:00
:EFFORT: 10d 0:00
:END:
- Takes an account as input and updates tags in all tables.
@ -109,17 +118,26 @@ Campaign proxy / rule service
*** Update tags in the subscriber tags table to conform to normalization rules
:PROPERTIES:
:Effort: 2d
:JIRA_ID: CCPANEL-12037
:END:
** Remove comparison normalization logic
:PROPERTIES:
:JIRA_ID: CCPANEL-12038
:END:
*** Remove normalized comparisons from Campaign Engine
:PROPERTIES:
:EFFORT: 4h
:JIRA_ID: CCPANEL-12039
:END:
*** Remove normalized comparisons from Analytics DB Search Terms
:PROPERTIES:
:EFFORT: 1d
:JIRA_ID: CCPANEL-12040
:END:
** [#B] Normalize tags stored outside of tagging and campaigns
:PROPERTIES:
:JIRA_ID: CCPANEL-12041
:END:
** [#B] Normalize externally stored tags
Optional based on product decisions. Tags will be normalized when ingested.
This should be done, but is not a blocker for the tag normalization project.

View file

@ -0,0 +1,4 @@
:PROPERTIES:
:ID: 0328a202-376d-4e97-b0e3-031eaad2a557
:END:
#+title: Overhauling logins and session management

15
daily/2022-03-10.org Normal file
View file

@ -0,0 +1,15 @@
:PROPERTIES:
:ID: 0bd45cf9-6965-45e8-add1-8907381b7ccc
:END:
#+title: 2022-03-10
* Discussing issues with [[id:57ee2f00-9bcd-4e0f-8a77-ae1f2d4cda89][CP]] session management
- How do we update things like the set of active lists that we currently cache
in redcache and the session?
- How do we solve for session issues as we work on [[id:0328a202-376d-4e97-b0e3-031eaad2a557][Overhauling logins and
session management]]?
It may be better to cache data on the client with browser storage and have the
front-end applications load data from the lists service. In theory, we could
emit events to the front-end application when objects update so that the client
can update its cache.