You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'll be downloading and playing with Tracks as soon as I get home. I'll probably host it both local and online (which gives rise to another task, to be recorded seperately)
Ideally, I'd be adding tasks to my family's accounts and they'd be adding tasks to mine - but certainly I don't want all tasks to be public - nor do I want all team (rather than personally) tasks to be accepted automatically.
So - if my partner adds a task for me to fix the broken shelf on the bookcase, I'd like to accept it, and prioritize it correctly, or reject it.
If I add a task to my babysitter's account, asking her to call and make a doctor's appointment with the pedi, I'd like to be able to see if it's accepted, completed, etc.
To me that implies both
logins authorized to add tasks - which would be given a status of submitted or pending, and other logins that are not permitted to submit tasks.
for logins that are permitted to submit tasks, the ability to review the status of their submitted tasks
public tasks that may be seen by all authorized members, and private tasks that are only visible to the account owner
in the context of teams - perhaps only tasks of a specified set that are also publicly visible, would be shown - that way the family can see family public tasks, the workgroup can see work public tasks, but not the opposit. (For my purposes, this is less important, as I intend to use it only for my personal and family productivity.)
Originally reported by Anonymous on August 8, 2006 at 18:25:32 (-0400)
The text was updated successfully, but these errors were encountered:
Migrated from the original issue at https://www.assembla.com/spaces/tracks-tickets/tickets/357
I'll be downloading and playing with Tracks as soon as I get home. I'll probably host it both local and online (which gives rise to another task, to be recorded seperately)
Ideally, I'd be adding tasks to my family's accounts and they'd be adding tasks to mine - but certainly I don't want all tasks to be public - nor do I want all team (rather than personally) tasks to be accepted automatically.
So - if my partner adds a task for me to fix the broken shelf on the bookcase, I'd like to accept it, and prioritize it correctly, or reject it.
If I add a task to my babysitter's account, asking her to call and make a doctor's appointment with the pedi, I'd like to be able to see if it's accepted, completed, etc.
To me that implies both
logins authorized to add tasks - which would be given a status of submitted or pending, and other logins that are not permitted to submit tasks.
for logins that are permitted to submit tasks, the ability to review the status of their submitted tasks
public tasks that may be seen by all authorized members, and private tasks that are only visible to the account owner
in the context of teams - perhaps only tasks of a specified set that are also publicly visible, would be shown - that way the family can see family public tasks, the workgroup can see work public tasks, but not the opposit. (For my purposes, this is less important, as I intend to use it only for my personal and family productivity.)
Originally reported by Anonymous on August 8, 2006 at 18:25:32 (-0400)
The text was updated successfully, but these errors were encountered: