emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: George Dowding <pyrios@gmail.com>
To: emacs-orgmode@gnu.org
Subject: timestamp variables
Date: Tue, 18 Oct 2016 11:59:51 -0400	[thread overview]
Message-ID: <CAM90rnd9f4K3NzJwYON3RTorf1XmTcPho5J8nFONhvSZ3LptKQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]

Hi,

I'm trying to create some TODOs in different projects with deadlines based
on different software releases. My initial thought would be to use a
variable to set the deadlines. The reason being that planned deadline
sometimes slips to a later date and I would like to update the deadline in
one place.

I'm open to organize things differently, but this example should show what
I a m getting at.

Right now, this is what I'm doing

* proj1
** TODO bug1
   DEADLINE: <2017-01-31 Tue>
** TODO bug2
   DEADLINE: <2017-01-31 Tue>
** TODO bug3
   DEADLINE: <2017-02-01 Wed>
* proj2
** TODO feat1
   DEADLINE: <2017-01-31 Tue>
** TODO feat2
   DEADLINE: <2017-03-01 Wed>
** TODO feat3
   DEADLINE: <2017-06-01 Thu>

But I would like to do something like this so that I can keep the project
work together and update the release deadlines in one place as they change.

* releases
** foo
   DEADLINE: <2017-01-31 Tue>
** foo.1
   DEADLINE: <2017-03-01 Wed>
** bar
   DEADLINE: <2017-06-01 Thu>
* proj1
** TODO bug1
   DEADLINE: <foo>
** TODO bug2
   DEADLINE: <foo>
** TODO bug3
   DEADLINE: <foo.1>
* proj2
** TODO feat1
   DEADLINE: <foo>
** TODO feat2
   DEADLINE: <foo.1>
** TODO feat3
   DEADLINE: <bar>

Thanks,
George

[-- Attachment #2: Type: text/html, Size: 1908 bytes --]

                 reply	other threads:[~2016-10-18 15:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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 \
    --in-reply-to=CAM90rnd9f4K3NzJwYON3RTorf1XmTcPho5J8nFONhvSZ3LptKQ@mail.gmail.com \
    --to=pyrios@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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 public 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).