1 Email vs T & L

Refresh Print   export
  * 101 use pw sys; open email; copy-paste pw; it stays open go to site; remembers + keeps me signed in [for a period] logging in to the system L + T significant advantage in avoiding the nuisance of open pw sys + subsequent steps L/T Prep go to site; remembers + keeps me signed in [so far]
| | | . . .
  * 108 create a new email; write the task; send it add a new Item; write the task defining a new task essentially the same; create email/Item/Card ~ TaskDef add a Card; write the task; +++
| | | . . .
  * 400 no particular method; must be done from Subject and body content in the initial email for the List the envelope info makes it clear that it's a task-do distinguishing a 'To Do' item from other communications getting To Do's out of the email stream [or distinguishing them far more clearly] is an added benefit L/T Comm should be clear from the Card communication
| | | . . .
  * 126 no particular method; state in the body who do the to do no assignment method in L; state in the description (or perhaps use a code-protocol in task-title) assigning 'Who Do' the To Do T far superior to email or L T TaskDef drag the name to the Card -- ???
| | | . . .
  * 110 using the Subject line usually title of the Item naming the task essentially equivalent ~ TaskDef title of the Card
| | | . . .
  * 112 in the email body in the Item Comment field describing the task essentially equivalent ~ TaskDef on back of the Card
| | | . . .
  * 120 seeing the Subject line in email list - zero context seeing the Item title in List of items; contexts: List; Category; Tags seeing the task in a list L+T far superior - this just does not work in email L/T Status seeing the Card title in List of Cards; contexts: position of Card on the List; position of List on the Board; ???
| | | . . .
  * 122 in Preview window or open the email [not see the narrative in a table format with the Subject ?] the List shows as a table: Item Name / Comment ... / narrative is visible in column in table-sheet seeing the narrative L+T far superior - this just does not work in email L/T Status click the Card to see 'back' of it
| | | . . .
  * 114 in body of email ['could' put in Subject; but not going to systematize that] shows a priority icon at end of line: Top; High; Normal priority indicator L is far superior - this just does not work in email L TaskDef drag-drop position in the List ???
| | | . . .
  * 116 could do it - but not going to 1st is List categorizes it; then Category categorizes it; + Tags function at List level categorization of tasks L is far superior - this just does not work in email L/T TaskDef Card is on a List / List position also / tags ??
| | | . . .
  * 124 nothing / email sys is already set up; just create an email have to first create a List; then (optionally) create a Category setup required before can create task email requires less set up; but L&T can handle many tasks under any one setup of List ... L/T TaskDef must create a List; after first creating a Board
| | | . . .
  * 130 send email / choose recipients - almost always Front Desk Team send email containing url of List containing task / choose recipients - same as 'email method' communicating/sharing the task ??? about same: task is written in email or in Listigator / Listigator requires extra small step of copy-paste the url T Comm auto email sent to the assignee ???
| | | . . .
  * 160 do Reply for the email / and re-Reply / etc etc / resulting in an email thread one method is to allow sharing to edit the task [Item] / they can extend the narrative (eg including keying in a date; etc); or even change the narrative / since it's just add text in the notes field it's vulnerable to sloppiness assignee response on the task L is MAJOR problem / E is better / T seems best T Response add Comment on Card ???
| | | . . .
  * 600     other elements see if need to consider other issues   Conclu  
| | | . . .
  * 650 not what i want / must be replaced the response problem is deal-killer OVERALL L wins a lot except the response problem; it was worth a brief trial; appears that T is at least 'workable' and perhaps even better than that T Conclu appears to be winner; with no deal-killer elements
| | | . . .
  * 128 send the email to Front Desk Team all having been sent the url of the List can observe ??? assigning observers for the task about the same ?? but L/T don't require a 'send' action for a new task [Item/Card] ??? ~ Prep all on the Board can observe ???
| | | . . .
  * 118 no grouping on assignment ['could' use codes; but not going to] [can use 'folders' and filters for email sorting] List required by structure; Category and Tags optional grouping of related tasks L is far superior - this just does not work in email L/T TaskDef List required by structure; +++ ??
| | | . . .
  * 132 email addresses already in Contacts / "Front Desk Team" already set as a group communication with team is through email - no extra set up is required communication set up required email + L simpler than T ?? E Prep requires (1) sending invitation to Board + (2) invitee doing registration on T [or accepting invite] ???
| | | . . .
  * 140 email can be sent to individuals; groups; or to public posting; etc email with link can be sent to individuals; groups; or public posting; etc sharing-mode options no real difference in sharing alternatives ~ Comm  
| | | . . .
  * 175 the Reply chain results in a good email thread the 'notepad'--like field is unformatted / a decent thread depends on formatting protocols integrity & history of the task L: chance of the original narrative and thread being irretrievably changed / comment box is like a notepad: no formatting for a 'thread' / email much superior to simply adding to the notes field in L T Prep the Comments thread seems to be good
| | | . . .
  * 104 usually the "Subject" of an "email" the title/name of an "Item" a task is id'ed as about the same ~ TaskDef the title/name on a "Card"
| | | . . .
   ___unknown_248043 [ v ] ___recovered_246784 [ v ] ___recovered_246785 [ v ] ___recovered_246786 [ v ] ___recovered_246788 [ v ] ___recovered_246789 [ v ] ___recovered_248069 [ v ] ___recovered_249969 [ v ]   
Select: 1-21, None
1-21 of 21 items   per page: 50 100 all    
close x

More options coming soon

loading...
close x

Track Changes

Keep up to date

RSS Updates: RSS

Publish:

Share this application

About this list:
No Description Available Yet

Comments: