From: Johnny <yggdrasil@gmx.co.uk>
To: Christian Egli <christian.egli@sbs.ch>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-taskjuggler export problems
Date: Mon, 07 Nov 2011 17:02:50 +0000 [thread overview]
Message-ID: <87wrbbamrp.fsf@gmx.co.uk> (raw)
In-Reply-To: <87mxc7lwy9.fsf@sbs.ch> (Christian Egli's message of "Mon, 07 Nov 2011 17:27:26 +0100")
Hi Christian and thanks for your response.
Christian Egli <christian.egli@sbs.ch> writes:
>
>> I am trying to export a simple project plan from org to taskjuggler
>> through org-taskjuggler.el. I cannot get the behavour I expect and
>> need do some manual tweaks to get the taskjuggler file working. What
>> am I doing wrong?
>
> You're not doing anything wrong. You've hit some bugs in the taskjuggler
> exporter.
>
>> 1) The 'end' date specified in the ':taskjuggler_project' base is ignored and
>> the default 280d is used. Because the project duration is long this
>> throws an error. The 'start' date however seems properly picked up.
>
> Indeed the end date is not picked up. I remember to have tried to fix
> this once, but the problem is that the root task serves as both a
> container for the project attributes and is a task at the same time. So
> if you define the end, you'll both define the end of the project and the
> task, which might not be what you want. Can you try to increase the
> org-export-taskjuggler-default-project-duration instead?
>
That is an acceptable solution. I guess the minor tradeoff is that by
having a large default value which is necessary for only one project
will transfer to others as well making the taskjuggler work harder. This
is not a major issue at all, but being able to specify on a per file
basis would be convenient.
>> 2) The 'task_id' fields are not exported properly.
>
> The taskjuggler exporter uses the task_ids you define just for
> dependency resolution. Other than that it creates automatic ids based on
> the title of the task. The assumption is that you are not that
> interested in defining ids. What do you need them for?
>
Well, dependency resolution is what I was after, but as the 'precedes'
is not exported that is the major culprit.
>> 3) The 'precedes' property is not exported at all
>
> Yes, this is not implemented. Could you use 'depends' instead? And
> possibly use alap scheduling?
It is not as transparent to use 'depends', as I have one milestone with
many tasks to be completed before. By using 'depends', I will (not
really) see in column view e.g. 20 tasks in the depends column. By using
'precedes', each task will be (much more) clearly mapped to the
milestone.
>
> Hope that helps
Yes, thanks for explaining how the export handles the fields.
Best,
--
Johnny
prev parent reply other threads:[~2011-11-07 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 16:19 org-taskjuggler export problems Johnny
2011-11-07 16:27 ` Christian Egli
2011-11-07 17:02 ` Johnny [this message]
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=87wrbbamrp.fsf@gmx.co.uk \
--to=yggdrasil@gmx.co.uk \
--cc=christian.egli@sbs.ch \
--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
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
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).