admin/sockeye
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2023-02-17 23:50:09 +00:00
parent 6ef28b47e9
commit 27a43e5e38
1 changed files with 19 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files

52
todo.txt
View File

@@ -1,37 +1,29 @@
TODO: TODO:
test trial request full flow - trial request full flow
ISSUE WITH EMAIL VERIFICATION NOT FOUND WHEN CLICK ON VERIFY ISSUE WITH EMAIL VERIFICATION NOT FOUND WHEN CLICK ON VERIFY
also it should email the user that their email was verified and they will be blah blahy working hours etc also it should email the user that their email was verified and they will be blah blahy working hours etc
also message if already verified should be already verified not not found / already verified also message if already verified should be already verified not not found / already verified
test v7 dummy sale
test a v7 fetch
REMOVE STAND UP CODE OR COMMENT IT OUT TO PREVENT ACCIDENTS
UNTESTED - REMOVE STAND UP CODE OR COMMENT IT OUT TO PREVENT ACCIDENTS
notifications on RAVEN trial request awaiting approval - test: notifications on RAVEN trial request awaiting approval
sub server create and track - test: sub server create and track
calendar event for decommission trial sub servers and notification - test: sub server open terminal from sockeye
Vendor notification route Test with v7 and v8 and test purchase vendor notification route with fake sales testsf - test: calendar event for decommission trial sub servers and notification
Everything again on release build - test: Vendor notification route Test with v7 and v8 and test purchase vendor notification route with fake sales testsf
- role rights fine tune to make more appropriate?
TESTED or at least review them to confirm
Raven
trial request entire flow including email validation - Subscribe to following notifications:
license generation manually and test installed Ops problem event should notify me immediately
server state first and second fails notify for starters but on a non alerting method so for FYI purposes
TODO BEFORE RELEASE server state 3rd fail should notify via some immediate and loud means regardless of time of day for starters
server state 3rd fail age of more than XX minutes should esclate to a secondary means of alerting, maybe email to text?
Re-test all of the above on ayanova.com server before flipping over from rockfish todo: see if email to text can be set at phone end to recognize sender as a spcecific contact and set a crazy loud any time alarm for it
copy of all howto docs to sockeye somewhere or ensure they are still available before final flip over, will need them
SERVER
supersock supersock
CLIENT
- Replace old rockfish docs site with something in sockeye so one place for all
@@ -78,13 +70,7 @@ FUTURE STUFF
- direct open a case by case number like workorder - direct open a case by case number like workorder
(id's differ so it isn't easy to just open a case in the url) (id's differ so it isn't easy to just open a case in the url)
WHEN RUNNING
- Subscribe to following notifications:
Ops problem event should notify me immediately
server state first and second fails notify for starters but on a non alerting method so for FYI purposes
server state 3rd fail should notify via some immediate and loud means regardless of time of day for starters
server state 3rd fail age of more than XX minutes should esclate to a secondary means of alerting, maybe email to text?
todo: see if email to text can be set at phone end to recognize sender as a spcecific contact and set a crazy loud any time alarm for it
LATER LATER