This commit is contained in:
@@ -79,5 +79,8 @@ Objects with one or more tags
|
||||
Objects that have a set of tags but do not have another set of tags
|
||||
Objects of a certain type but any id that have a certain tag
|
||||
|
||||
V7IMPORT
|
||||
See case 3373 for a list of things that will become tags
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -2,9 +2,11 @@ DISPATCH ZONE SPECS
|
||||
|
||||
CASES
|
||||
|
||||
3472, 3473, 3439
|
||||
3472, 3439
|
||||
|
||||
REQUIREMENTS
|
||||
|
||||
Dispatch zones will be a collection now for users and also will replace scheduleable user groups
|
||||
Dispatch zones will be replaced by tags now for users and also will replace scheduleable user groups
|
||||
I've examined the use cases, v7 usage, new cases for raven and nothing indicates we can't use tags for this with the added feature of tag groups which is a good idea anyway.
|
||||
TAGS all the things!!
|
||||
|
||||
|
||||
@@ -18,7 +18,8 @@ Changes needed to routes??
|
||||
CODING WORK
|
||||
+++++++++++
|
||||
|
||||
Overall plan for now: anything standing in the way of making the initial client shell UI needs to be done first, everything else can wait
|
||||
Overall plan for now: anything standing in the way of making the initial client shell UI needs to be done first, everything else can wait
|
||||
- V7Import Dispatch zones (as tags), ScheduleableuserGroup (as tags) so can be used with User import and other shit
|
||||
- Event log make sure can set the date and time to prior values for importing
|
||||
- v7importusers
|
||||
- User route and controller and biz object
|
||||
|
||||
Reference in New Issue
Block a user