Would suggestion 1 apply only when a task is created using the "new
task" button and the menu equivalents (task>new task; task>new subtask;
Ins; Alt+Ins)?
How about New Folder, New Project, and don't forget New From Template.
Would it apply for tasks created through the RTE window?
Would it apply to tasks emailed in through TBE?
How about tasks moved via drag & drop? Or cut/copy and paste? or the
Move To/Ctrl M command?
For inherited fields resulting from a copy or move command, when
inheriting a value in a field that can have multiple values (dependency,
context) would the new (inherited) value replace the existing value or
be appended to it?
For each of these questions there are probably existing users who could
only live with "yes" and others who could only live with "no" so if you
are answering too quickly go back and think through the implications of
each choice: what sorts of things will be enabled or disabled by each
choice.
And finally, be careful to avoid over-reliance on asking for a new
setting so that users can configure their personal choice for each
answer\. It's kind of a coward's answer, adds a lot of costs to the
development, adds to the complexity of the software, makes it hard to
understand and intimidates potential users
-Dwight
On 9/7/2016 8:10 PM, John . Smith wrote:
In MLO Windows...
Hello
I suggest MLO needs:
SUGGESTION 01) An new Option that offers the user a list showing
the *full list *of *task fields* so that the user can choose which
fields do and which do not inherit their values when a new task is
created. I suggest that these values should probably default from the
parent task.
SUGGESTION 02) However even better, the user should be given a further
option of choosing where these values inherit from
a) The currently selected task
b) The parent of the selected task
SUGGESTION 03) Another useful option would be to give the option for any
date fields to default now/today.
SUGGESTION 04) And another useful option would be to make the fields
'cascade'.
i.e. If the field is changed on a task that already has children, then
all children tasks (and grand-children etc) would take on the value of
that field.
This can be particularly useful for the Star field or any other field
being used for "focus on today".
Background
For me personally "Suggesion 01)" is a /*huge */issue, as it would
finally allow me to use to use Flag fields for GTD Action Status
(Active, Someday, Waiting etc). Without this feature, despite my
spending about 12 months of my life on MLO, I still have failed to get a
satisfactory implementation of the GTD method when I am using a fairly
large number (400+) tasks on my system.
Any takers?
J
--
You received this message because you are subscribed to the Google
Groups "MyLifeOrganized" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at https://groups.google.com/group/mylifeorganized.
To view this discussion on the web visit
https://groups.google.com/d/msgid/mylifeorganized/0a092c61-ce4d-4018-8b5e-6e6dccbc6531%40googlegroups.com
<https://groups.google.com/d/msgid/mylifeorganized/0a092c61-ce4d-4018-8b5e-6e6dccbc6531%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"MyLifeOrganized" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/mylifeorganized.
To view this discussion on the web visit
https://groups.google.com/d/msgid/mylifeorganized/7ed5cd30-503a-b55a-ec4d-0117aad17aff%40dwightarthur.us.
For more options, visit https://groups.google.com/d/optout.
