From 406b2d7d216285fb3854a0d9de83435c4db4c8cf Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Mon, 7 Jun 2021 22:18:22 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 16 +++------------- 1 file changed, 3 insertions(+), 13 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index a4f2ea87..16c4bbc1 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -367,19 +367,9 @@ todo: many biz objects are not using new PUT methodology CURRENTLY DOING: workorder round two electric boogaloo basics first then increasingly esoteric features -todo: a mixup between "not finished" wording and code and actual "Close by date" on work order header - Seems as though some areas are coded / planned based on creation date of workorder rather than on closeby date - in fact close by date isn't even factored into any planned v8 notification which is just wrong - Creation is factored into not finished but created means nothing on it's own or should be a separate notification like age or somethign - so change everythingn related to "finished" to be worded as "close by" to eliminate confusion e.g.: - "NotifyEventWorkorderFinishStatusOverdue": "Work order not finished in time", - - Go over code and plans and enums and make sure it all lines up with close by. - - Also, close by is a bit out of sync with the wo status wording of "Completed" which is what I decided was a better term, so maybe the workorder field should not be "close by" but - "complete by" - - Then after above can implement the notification properly which currently is using creation date for calcs +todo: tag based notifications need to be rechecked if tags change, not just the field(s) in question for that notification + for example, user makes a workorder with closeby date and tags but tags don't match when saves + user realizes missed a critical tag, adds it and saves; notification should then check again if can apply whatever it was todo 3: notification Go through all notification types and pick out relevant ones, paste here in a list then implement one by one and test each