On Thursday, 21 April 2016 07:47:40 UTC+1, Tolqua wrote:
>
> I've just started using MLO, syncing between my Windows desktop and Nexus 
> 5 via Wi-Fi.  I'm fine with using ad-hoc tasks and organising them in 
> Outline view, but I now want to set up a system to deal with a particular 
> type of recurring tasks.
>
> I have noticed that there are two or three times in my day where a 
> ‘checklist’ of items to be completed would be extremely useful (e.g. Before 
> going to work, Before going home, etc.).  The items on the list would all 
> be recurrent items, but with differing patterns (e.g. every working day, 
> every three days, alternate Wednesdays, etc.) so each day’s lists will be 
> different – or different enough that a repeat cycle could be potentially 
> very long.
>
>  
>
> The items on the lists would all be simple tasks without sub-tasks 
> (probably) that simply need to be checked off – whether that’s achieved by 
> marking a task complete or simply by putting a check mark in a box is not 
> important.  What is important is to have the lists appear on my To Do 
> list or Action List as just the checklist name (e.g. Morning Checklist) 
> with the items on the list hidden until the list is opened.  This is 
> important so that the space on my daily Action List isn’t filled with all 
> the regular routine stuff on the checklists.  The checklist should 
> probably have a reminder.  Since I’m in the habit of checking the status 
> bar at the top of my Nexus 5 whenever I pick it up, this tends to be my 
> immediate action list as it’s available to all apps, not just MLO.  The 
> reminder, unless Snoozed or Cancelled, should take me straight to the open 
> checklist or to the Action List with the checklist highlighted so that one 
> more tap would open up the checklist ready for me to go through the things 
> on the list.  The list would need to stay open or be available until I’d 
> checked off all the items, at which point the checklist would disappear 
> from the Action List until the next day (or be greyed-out or changed in 
> some way so it’s clear it’s complete).  
>
>  
>
> I'm not sure whether the checklist itself would need a recurrence pattern 
> and how it would relate to the recurrence patterns of the items, but in the 
> unlikely event that none of the checklist items was due to appear on the 
> list, the list should either appear empty or not appear at all.
>
>  
>
> It doesn't sound too complicated and I'm sure it's well within the 
> capabilities of MLO, but I need some guidance as to the best way to set it 
> up.  Should I make each checklist a Project with the items as Tasks or 
> make each checklist as a Task with the items as Sub-Tasks?  How do I have 
> the checklist appear on the To Do List, but hide the items until the 
> checklist is opened?  How can I have the checklist disappear when all the 
> items have been either checked off or ‘skipped’ (not done, but with the 
> next occurrence in the pattern generated)?
>
>  
>
> There may be many ways to achieve this and I’m sure I’ll have a lot more 
> questions once I start using it, but for now I just need to get it up and 
> running enough to be able to start working with it on a daily basis so any 
> help/suggestions will be most welcome.
>
>
> Tolqua.
>
>
>

-- 
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 mylifeorganized+unsubscr...@googlegroups.com.
To post to this group, send email to mylifeorganized@googlegroups.com.
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/60d4fd12-0710-4df1-bd68-e22e54241344%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to