ayanova/devdocs/todo.txt

@@ -55,6 +55,9 @@ todo: v8 migrate additions
 
 ## CLIENT MISC ITEMS
 
+todo: be sure top address items in case https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3864 
+	before next update to server / windows build for Joyce
+
 todo: Re-test reporting on linux, just updated puppeteer sharp and it might be affected due to newer chromium
 
 todo: REPORTING
@@ -253,11 +256,16 @@ todo: many biz objects are not using new PUT methodology
 
 
 CURRENTLY DOING: 
-	front end back end update all the things, it's overdue then back to this stuff again
 
 
 OVERALL	
-	- Test out role rights, login as various roles and ensure it works as expected
+	- fixup status control 
+		status control should require click to open dialog which shows list of all status prior and allows to add then close to view
+		this way it's clear how to change, less confusing than now and easy to get at the list
+	- woitemtask UI question
+		is this really a collection like scheduled users or labors now??
+		Does it show on a main table in it's own form??n
+
 	- once past this step then second pass at new features **that affect models** (not necessarily UI stuff just fields required etc)
 		Add items below that are just spurious and not tied to a particular case as v.next cases YAGNI/TTM!	
 	- then full in front end and flow out to back end as required, remove any backend that was a defunct evolutionary path so no cruft left around
@@ -266,29 +274,21 @@ OVERALL
 	- ## Try to find every thing that will matter when more collections are added now, ensure a full flow from start to stop and everything in between to try to catch any gotchas now before get too deep into it ##
 
 
-todo: update on save??
-	can it fetch down changes or does that even make sense bandwidth wise
-		No ttm yagni etc etc
-		can be looked at as a v.next issue
 
-
-todo: WorkOrderItemTask??
-	is this really a collection like scheduled users or labors now??
-	Does it show on a main table in it's own form??
+	
 
 todo: changing scheduser estimated qty doesn't trigger dirty until move off, is it using the wrong event for update?
 	gz-decimal control
+
 todo: introduce menu item for woitem table descendant view (not wired up yet, just there to remind and as placeholder)
-
-
-todo: status control should require click to open dialog which shows list of all status prior and allows to add then close to view
-	this way it's clear how to change, less confusing than now and easy to get at the list
+ 
 
 todo: can I turn control labels into hyperlinks for getting to feeder records?  If not then need to find a way to accomplish it        
 		e.g. can workorder status title be changed to a hyper link to status list
 		e.g. can projects title be turned to a hyper link to projects list
 		ideally not in menu because it would be a lot on a workorder and need space for wo graph subitem links   
 		### I ALREADY have an affordance for this with the pick lists, JUST replicate that!!
+
 todo: Translations stuff 
 	- "delete selected item" text instead of "Delete" for subitems
 	- workordercustomX translation keys not set yet, just copy workorderItem ones I guess
@@ -389,8 +389,7 @@ Preliminary order to get the ball rolling, these are the easiest starting point:
 	this way (last thing) we are always covered no matter what happens with wo import etc
 
 
-	WorkorderStatus
-		no dependencies, possibly many cases, read over carefully before implementing
+
 
 	Workorder
 		When do this need to go back and do a bunch of //MIGRATE_OUTSTANDING