diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt
index 73061160..a3869778 100644
--- a/ayanova/devdocs/todo.txt
+++ b/ayanova/devdocs/todo.txt
@@ -6,13 +6,6 @@ WIFI change 5g channel to 52,56,60 and 2g channel to 8
 	recheck before doing as it seems to vary, maybe someone else's is auto switching
 
 
- 
-todo: Are UTC filters really working properly?	
-	Check that a datafilter with dates incoming datetime ranges are either interpreted as UTC on route (from post formdata maybe, already know query params are NOT)
-		or that at some point in the chain they are converted to UTC like metricmm is doing on filter query
-	I'm seeing weirdness with the metrics that makes me think the server is not filtering in UTC but converting the incoming datetime / assuming local
-	Make a date filterable record confirm it properly finds based on time
-
 todo: server state has a "more" icon in menu inexplicably
 
 
diff --git a/ayanova/src/components/gz-data-table.vue b/ayanova/src/components/gz-data-table.vue
index a54a2897..45544e87 100644
--- a/ayanova/src/components/gz-data-table.vue
+++ b/ayanova/src/components/gz-data-table.vue
@@ -963,14 +963,14 @@ function untokenizeListView(lvJson) {
           //AFTER DATE?
           if (filterDates.after) {
             reto.filter.items.push({
-              op: ">=", //GreaterThanOrEqualTo
+              op: ">", //was GreaterThanOrEqualTo but that doesn't make sense, it's only greater than was seeing wrong return data as relative date filter already adjusts for boundaries
               value: filterDates.after
             });
           }
           //BEFORE DATE?
           if (filterDates.before) {
             reto.filter.items.push({
-              op: "<=", //LessThanOrEqualTo
+              op: "<", //was LessThanOrEqualTo but see above for after ===-----^
               value: filterDates.before
             });
           }