ayanova/devdocs/todo.txt

@@ -3,8 +3,6 @@
 PRIORITY - ALWAYS Lowest level stuff first, i.e. TODO at server, api route changes etc then back here in order lowest level first as affects the most stuff exponentially so best to do it early
 =-=-=-=-
 
-
-
 todo: notification
 	https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3783	
 	notifications list UI as per case
@@ -15,9 +13,8 @@ todo: notification
 		Client related routes at server
 			Seen, fetch, delete etc
 
-	create notifications at server for ops stuff in todos once back end is coded
-
 
+todo: create notifications at server for ops stuff in todos once back end is coded
 
 todo: client global settings notification systemactive
 	Needs to get data from api as well as UI to control it and translation key for NotificationSystemActive
@@ -30,6 +27,12 @@ todo: send test notification from both ops and admin pages
 	also from client users form
 	Will then issue warning if either OPS smtp notification is turned off (Active=false) or Admin NotificationSystemActive is turned off
 
+
+
+
+
+
+##########################
 todo: Customer User list form side track but relevant to this
 	Have to decide, do I list all users in the Existing users list form including customers?
 	Or, is it done via the Customer themselves?
@@ -48,7 +51,7 @@ todo: Test server down while polling in release mode, does it recover when serve
 todo: read only version of duration, datetime, date, time, currency
 
 
-todo: pick lists in forms should be sortable alphabetically
+todo: pick lists in forms should be sortable alphabetically *at the client end* as default but optionally turn off so for things that are a definite order not alphabetic can turn off
 	for example the event types and object types in notification subscription
 
 todo: does Duplicate code really duplicate the tags?