emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Christian Egli <christian.egli@sbs.ch>,
	emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Setting taskjuggler project start date (ox-taskjuggler)
Date: Wed, 27 Mar 2013 17:00:08 -0500	[thread overview]
Message-ID: <CA+M2ft8HnVmQB5-Hq-BLutNH5viSQ3HT4bVpR2k_PJnueFD48g@mail.gmail.com> (raw)
In-Reply-To: <87sj3ggb8j.fsf@gmail.com>

On Wed, Mar 27, 2013 at 9:37 AM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> Hello,
> John Hendy <jw.hendy@gmail.com> writes:
>> If you have =org-taskjuggler-keep-project-as-task=, it will take the
>> :start: property and use this in the project-as-top-level-task output.
>> Could this be used after =scheduled= and before defaulting to today's
>> date? This would seem to unify the syntax.
>> It strikes me as reasonable to take 1) scheduled, 2) :start: in
>> property drawer and 3) default to today's date (in that order).
>> What do you think?
> I don't know much about TaskJuggler. It doesn't sound unreasonable to
> me, but I'd rather let Christian Egli (Cc'ed) decide about it.

Sure. The gist is that you define a "range" for the overall project.
My issue probably stems from the fact that I'm using the functionality
simply for the organizational aspects of Org-mode vs. writing all that
TJ code manually. I *haven't* (so far) been actually using TODOs or
SCHEDULED/DEADLINEs on my headers, which may be why I was surprised at
the functionality. I'm more using the property drawers to just
manually access the keywords allowed via the TJ syntax.

Since others might be doing this (and the tutorial doesn't suggest to
use Org-mode scheduling functionality)... might be good to at least
allow for it.

Also, since I noticed that my tasks pick up the :start: property and
that the get-start (item) function *could* pick up a scheduled date as
well... might be good to anticipate the case in which the user
specifies both (probably accidentally). Maybe just provide an error
that either scheduled/deadline *or* :start: should be used, but not

Or if scheduled date conflicts with an duration/dependency relationship as well?

Some of this might be handled by the tj3 command on the resultant .tjp
file, though. I've found that the export is pretty strict and it will
with most cases like this.


> Regards,
> --
> Nicolas Goaziou

  reply	other threads:[~2013-03-27 22:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25  6:27 John Hendy
2013-03-25  7:17 ` John Hendy
2013-03-25  7:30   ` John Hendy
2013-03-25 20:15     ` Nicolas Goaziou
2013-03-25 22:14       ` John Hendy
2013-03-27 14:37         ` Nicolas Goaziou
2013-03-27 22:00           ` John Hendy [this message]
2013-04-24  8:30             ` Christian Egli

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:

  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=CA+M2ft8HnVmQB5-Hq-BLutNH5viSQ3HT4bVpR2k_PJnueFD48g@mail.gmail.com \
    --to=jw.hendy@gmail.com \
    --cc=christian.egli@sbs.ch \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    --subject='Re: Setting taskjuggler project start date (ox-taskjuggler)' \


* 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:


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).