This commit is contained in:
52
todo.txt
52
todo.txt
@@ -1,37 +1,29 @@
|
||||
TODO:
|
||||
|
||||
test trial request full flow
|
||||
- trial request full flow
|
||||
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 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
|
||||
notifications on RAVEN trial request awaiting approval
|
||||
sub server create and track
|
||||
calendar event for decommission trial sub servers and notification
|
||||
Vendor notification route Test with v7 and v8 and test purchase vendor notification route with fake sales testsf
|
||||
Everything again on release build
|
||||
|
||||
|
||||
TESTED
|
||||
Raven
|
||||
trial request entire flow including email validation
|
||||
license generation manually and test installed
|
||||
|
||||
TODO BEFORE RELEASE
|
||||
|
||||
Re-test all of the above on ayanova.com server before flipping over from rockfish
|
||||
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
|
||||
- REMOVE STAND UP CODE OR COMMENT IT OUT TO PREVENT ACCIDENTS
|
||||
- test: notifications on RAVEN trial request awaiting approval
|
||||
- test: sub server create and track
|
||||
- test: sub server open terminal from sockeye
|
||||
- test: calendar event for decommission trial sub servers and notification
|
||||
- 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?
|
||||
or at least review them to confirm
|
||||
|
||||
- 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
|
||||
|
||||
|
||||
- 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
|
||||
(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
|
||||
|
||||
|
||||
Reference in New Issue
Block a user