diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index cb58fdbe..75e708b1 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -356,6 +356,9 @@ CURRENTLY DOING: workorder round two electric boogaloo
 	state of things, re-prioritize
 
 
+todo: itemize and implement missing "fringe" features from v7 that are just there for workorders but not implemented yet in v8
+
+
 todo: workorderitemlabor new record stop date sb +1 hour
 
 todo: stop hiding one line tables in wo form, need them for the extra ui stuff they bring
@@ -411,6 +414,9 @@ todo: subcontractor not seeing prices but still able to make workorder case (not
 	(Or, if it's just hiding cost fields then just don't populate viz them. Viz fields can be safely set to anything really)
 
 todo: signature: report helper display signature and form ui control to capture /display signature 
+	for both tech and customer
+	case 2052 is this one
+
 TODO: Test address / units select alternate when have units working
 TODO: Sequence field sb hidden by default, most won't want it I'm guessing
 	really need to pin down some default form customization for wo
@@ -431,8 +437,16 @@ CASES TODO:
 	1908 - set new durationtocompleted field on wo header upon setting to a closed status, also show it in the main data list
 	1961 - auto remove from inventory immediately when wo saved and re-instate if changed
 		see PO back end for example of exactly this
-
-	
+	3374 - be able to move woitem to any customer's open workorders not just the same customer.
+		not sure of the use of this, it's couched like a template issue which is what template is for, but since we no longer force 
+		a fixed customer per workorder there's no reason I can see not to do this when implementing the Move woItem feature
+	3445 - copy selected tasks to a labor record 
+		it says selected but I wonder about just doing all and they can simply edit out the ones they don't want?
+		(otherwise need checkboxes and whole selection thing but I guess if it's doable...)
+	3500 - implemented but needs the docs and seed data to illustrate the feature
+		make a shadow units customer in seeder sample data
+		make units under shadow units customer
+		assign some loan items to those shadow units