Closed aclark4life closed 9 years ago
Got it, thanks. So if I understand correctly: we'll still be adding a "Task planner" type to uu.task with the features you describe. And we'll leave UUTask folder-ish unless UI/UX becomes too problematic.
Agreed.
The biggest challenge for "task planner" (since it is just a dumb folder with some fields and a view) is figuring out which schema fields are shared between task and planner, and making sure our behavior interfaces reflect that (with some kind of sane inheritance hierarchy).
For task nesting, we can punt on worrying about any UX issues for the moment, they are not a high priority (and they can be solved in such a way in the future that allows the type to still be folderish).
@seanupton Can you make a list here of some tentative fields to share between task and planner? I'll get started adding them and thinking about sharing. Thanks
Short version: assigned principal(s) plus everything listed in the view mock (except/minus the top line of specific due date/time, which is only sensible for a specific event, not a group/series of them): https://github.com/upiq/uu.task/blob/master/doc/due-notification-rules.png
@garbas Fields to share between Task Planner and contained Tasks are loosely defined here.
This is done via IInheritParentValue
marker interface defined here: https://github.com/upiq/uu.task/blob/master/uu/task/interfaces.py#L84 and used here:
Relevant comment from @seanupton