emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: david whiting <dw@davidwhiting.me.uk>
To: emacs-orgmode@gnu.org
Subject: ox-taskjuggler scenarios
Date: Sat, 12 Jun 2021 07:10:09 +0100	[thread overview]
Message-ID: <CAK8-SWQSvFMpwOy7NBQzXMU9mQXq1LCk-9c1K-x2dMwjz+jSeQ@mail.gmail.com> (raw)


I am starting to use org-mode with taskjuggler and am trying to
implement scenarios. To work with scenarios I need to be able to
provide the scenario parameter values where the scenario differs to
the default plan. For example, using the example from
there are two scenarios, called "actual" and "test". To apply
different values to show the base scenario/plan, what actually
happened and the test scenario, I would do something like this:

task t "Task" {
  start 2007-05-29
  actual:start 2007-06-03
  test:start 2007-06-07

In this example, the original plan was to start on 2007-05-29, the
project actually started on 2007-06-03 and we also get to see what
would have happened if we started on 2007-06-07.

Using org-mode I can use the following to create the task with the
planned start date:

*** Task
    :start: 2007-05-29

But I haven't been able to add the actual and test scenarios. I need
to be able to add something like:

*** Task
    :start: 2007-05-29
    :actual:start: 2007-06-03
    :test:start: 2007-06-07

But the actual and test information is ignored, it is not converted in
the tjp file. I have tried adding "actual:start" (without the quotes)
to org-taskjuggler-valid-task-attributes, but that did not work. I
have also tried a similar approach with "effort", but again it is

I currently have a hack to get what I want. I add the scenario info as
a comment with a marker and then run a sed script on the resulting tjp
file to replace the comment-markers with \n, like this:

*** Task
    :start: 2007-05-29 #@actual:start 2007-06-03 #@test:start 2007-06-07

Is there a better way to do this?

David Whiting

             reply	other threads:[~2021-06-12  6:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-12  6:10 david whiting [this message]
2021-06-13  0:11 ` ox-taskjuggler scenarios Tim Cross
2021-09-26 14:06   ` Bastien

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=CAK8-SWQSvFMpwOy7NBQzXMU9mQXq1LCk-9c1K-x2dMwjz+jSeQ@mail.gmail.com \
    --to=dw@davidwhiting.me.uk \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public 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).