From: Tim Cross <email@example.com> To: Karl Voit <news1142@Karl-Voit.at> Cc: firstname.lastname@example.org Subject: Re: @name-tags instead of TODO keywords to assign people (was: Org mode for meeting minutes) Date: Mon, 04 Nov 2019 08:03:21 +1100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <2019-11-03T21-44-51@devnull.Karl-Voit.at> +1. This is how I do it as well. This approach makes it easier to not only see what tasks have been assigned to what people, it also provides a way to generate a custom agenda (report) showing what tasks each has and what the state is for each task. Tim Karl Voit <devnull@Karl-Voit.at> writes: > * Christian Egli <firstname.lastname@example.org> wrote: >> >> The idea is that you use type todos using the people involved at the >> meeting. Below is an example how this could look: >> >> ``` org >> #+title: Meeting minutes >> >> #+TYP_TODO: Fred Sara Lucy Mike | DONE > > I'd challenge the decisions on using TODO keywords for people > although the Org manual also suggests to do so. > > TODO keywords are single classification. This means that you are not > able to assign more than one person to a task. I'm using @tags for > the same purpose which allows me to assign tasks to more than one > person and keep TODO keywords independent to the person. For > example, when you resolve a task, you lose the information who was > assigned to the task. > > Therefore, I'd use: > > * Meeting > > ** TODO Prepare the demo :@Fred: > ** STARTED Contact customer :@Sara: > ** TODO Work on the document :@Fred:@Lucy:@Mike: > > More on that on > https://karl-voit.at/2019/09/25/categories-versus-tags/ including an > elisp snippet I'm using to filter according to @name-tags. > > YMMV. HTH. -- Tim Cross
next prev parent reply other threads:[~2019-11-03 21:03 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-31 14:03 Org mode for meeting minutes Christian Egli 2019-10-31 15:49 ` Fraga, Eric 2019-10-31 17:11 ` Ken Mankoff 2020-03-23 9:36 ` Christian Egli 2020-03-23 11:39 ` Eric S Fraga 2020-03-23 13:33 ` Axel Kielhorn 2020-03-23 13:47 ` Carsten Dominik 2020-03-23 18:09 ` Pankaj Jangid 2020-03-23 22:00 ` Nick Dokos 2020-03-24 10:09 ` Pankaj Jangid 2020-03-23 20:03 ` Timm Lichte 2020-03-24 10:04 ` Christian Egli 2020-03-25 22:39 ` Timm Lichte 2020-03-26 8:28 ` Christian Egli 2020-03-24 11:19 ` Eric S Fraga 2020-03-24 12:00 ` Eric S Fraga 2020-03-25 17:55 ` Bob Newell 2020-03-25 19:02 ` Diego Zamboni 2019-11-01 12:49 ` John Kitchin 2019-11-03 20:49 ` @name-tags instead of TODO keywords to assign people (was: Org mode for meeting minutes) Karl Voit 2019-11-03 21:03 ` Tim Cross [this message] 2020-02-12 9:12 ` Org mode for meeting minutes Bastien 2020-07-07 11:44 ` Adam Spiers 2020-07-07 16:21 ` Alexander Adolf
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --cc=news1142@Karl-Voit.at \ --subject='Re: @name-tags instead of TODO keywords to assign people (was: Org mode for meeting minutes)' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).