diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index 96907d09..2de69059 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -52,22 +52,36 @@ CURRENT TODOs
 
 todo: See if any priority 1 cases in Rockfish impact what is in teh Widget form menu or shell in general
 	- Stub out or add anything now before get too deep
+	- MRU in dashboard...where? https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3723
+	-
 
 todo: WIKI	
 
 todo: ATTACHMENTS
-	
+	- ability to rename file on upload https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3546
+	- stuff https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3484
+	- handle initially missing files on import (they might fuck up the export from v7, ghost files idea see case in AyaNova regarding datadump)
+
+TODO: PRIORITIZE THE FOLLOWING BLOCK INTO STAGES
+(these items came up looking through the raven priority 1 cases for general UI stuff)
+
+todo: Login form customizable for logo etc?
+	- https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3592
+	- possibly other cases?
+
+todo: Customer UI pages ability to add analytics tracking codes:
+	https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3574
+
+todo: add long polling notification route
+	https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3507
 
 
 
 RETEST HERE ON ALL DEVICES
 
-todo: AUTOMATIC TEST *** SUPER IMPORTANT *****
-	- Once widget form is solid then need an automatic UI test for it to get that ball rolling and to ensure no slips during development
-		- Ideally it will test every input component and validate the entire record round trips properly, maybe it needs to also try different states like creating new, editing etc
-	- Also function as a "smoke" test that will heavily exercise the server and client repeatedly for as long as I let it run which will reveal issues before releases
 
 todo: translation page with translation settings
+	- Translation feedback link in translation page https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3722
 
 todo: Trial route ui support in client (ON HOLD NEEDS BACKEND WORK)
 	- Went to do this but found it's a bit of a maze and has some hacked temp code in the license fetch route etc for development purposes
@@ -194,6 +208,8 @@ todo: Report editor for creating new report accessed from the report any **exist
 	- or maybe from the report selector dialog box if they have the rights, although would that fuck up navigation process?
 		- This seems better because, what if they can't preview a report for some reason, then they can never fix it or make a new one?
 	- NOT like v7 where accessed from the object edit form (this is to keep menu options down to a reasonable number)
+	- Every list sb reportable case https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3653
+		- Also search results and history?  Can feed from UI level to report component?