This commit is contained in:
@@ -56,7 +56,7 @@ todo: workorders - need to set billing and service address from customers on mig
|
|||||||
## CLIENT MISC ITEMS
|
## CLIENT MISC ITEMS
|
||||||
|
|
||||||
todo: notifications screen add delete all menu item that will just remove all the notifications present
|
todo: notifications screen add delete all menu item that will just remove all the notifications present
|
||||||
|
todo: notifications new count seems to be double getting on each iteration
|
||||||
todo: Seeding UI keep track of timing and later down the road when firmed up, provide estimate (average server will take):
|
todo: Seeding UI keep track of timing and later down the road when firmed up, provide estimate (average server will take):
|
||||||
2021-05-31 10:26:45.4801|INFO|Seeder|Small level sample data seeded in 27 seconds
|
2021-05-31 10:26:45.4801|INFO|Seeder|Small level sample data seeded in 27 seconds
|
||||||
2021-05-31 10:47:07.3417|INFO|Seeder|MEDIUM level sample data seeded in 2 minutes and 13 seconds
|
2021-05-31 10:47:07.3417|INFO|Seeder|MEDIUM level sample data seeded in 2 minutes and 13 seconds
|
||||||
@@ -371,10 +371,22 @@ todo: many biz objects are not using new PUT methodology
|
|||||||
|
|
||||||
|
|
||||||
CURRENTLY DOING: workorder round two electric boogaloo
|
CURRENTLY DOING: workorder round two electric boogaloo
|
||||||
basics first then increasingly esoteric features
|
basics first then increasingly esoteric features
|
||||||
|
|
||||||
|
CHECK IF BIZADMIN, ACCOUNTING AND SUPERUSER get two workorders overdue notifications
|
||||||
|
|
||||||
|
TODO: work orders with complete by dates set in the past should NOT notify??
|
||||||
|
accidental mistake could trigger rampant notifications, but then maybe there is a realistic case for this??
|
||||||
|
which is better to not use it because it's likely an accident or old import or use it so user can see mistake right away??
|
||||||
|
|
||||||
|
Tested:
|
||||||
|
Overdue notification works with one user subscription
|
||||||
|
changing the close by date / time re-issues overdue notification
|
||||||
|
|
||||||
|
|
||||||
Testing:
|
Testing:
|
||||||
Be sure to test with multiple subscribers and also inactive subscribers to ensure it does what it says on the box
|
Be sure to test with multiple subscribers and also inactive subscribers to ensure it does what it says on the box
|
||||||
|
Test with tags on each one to make sure that works as well
|
||||||
status changed to specific status immediate notification
|
status changed to specific status immediate notification
|
||||||
complete by overdue - make sure that contract sets complete by date properly and that it works with notification when it's changed
|
complete by overdue - make sure that contract sets complete by date properly and that it works with notification when it's changed
|
||||||
status age, stuck in status
|
status age, stuck in status
|
||||||
|
|||||||
Reference in New Issue
Block a user