From: Johnny <yggdrasil@gmx.co.uk>
To: emacs-orgmode@gnu.org
Subject: org-taskjuggler export problems
Date: Thu, 03 Nov 2011 16:19:53 +0000 [thread overview]
Message-ID: <8739e5kwk6.fsf@gmx.co.uk> (raw)
Hi,
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. The
questions are as follows, whereafter the test org-file that I attempt
export and finally the tweaked taskjuggler file that I was expecting to
see from the 'org-export-as-taskjuggler'. What am I doing wrong?
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.
2) The 'task_id' fields are not exported properly.
3) The 'precedes' property is not exported at all
Taskjuggler version is 2.4.3 org version is 7.7.
Thanks,
J
# ORG testfile follows------------------
#+STARTUP: hidestars
#+STARTUP: outline
* Assessment findings (electrical)
:taskjuggler_project:
:PROPERTIES:
:start: 2011-06-01
:end: 2014-06-01
:COLUMNS: %23ITEM(Task) %task_id %precedes %start %5Effort
:END:
** Tasks
*** Task A
:PROPERTIES:
:task_id: task_A
:precedes: mils_A
:Effort: 10d
:END:
*** Task B
:PROPERTIES:
:task_id: task_B
:precedes: mils_B
:Effort: 10d
:END:
*** Task C
:PROPERTIES:
:task_id: task_C
:precedes: mils_B
:Effort: 10d
:END:
** Milestones
*** Milestone A
:PROPERTIES:
:task_id: mils_A
:start: 2012-01-01
:END:
*** Milestone B
:PROPERTIES:
:task_id: mils_B
:start: 2013-01-01
:END:
# Tweaked taskjuggler file follows------------------
project assessment "Assessment findings (electrical)" "1.0" 2011-06-01
+2800d {
}
shift s40 "Part time shift" {
workinghours wed, thu, fri off
}
resource jim "jim" {
}
task assessment "Assessment findings (electrical)" {
purge allocations
allocate jim
start 2011-06-01
end 2014-06-01
task tasks "Tasks" {
task task_a "Task A" {
effort 80.0h
precedes !!milestones.mils_a
}
task task_b "Task B" {
effort 80.0h
precedes !!milestones.mils_b
}
task task_c "Task C" {
effort 80.0h
precedes !!milestones.mils_b
}
}
task milestones "Milestones" {
task mils_a "Milestone A" {
milestone
start 2012-01-01
}
task mils_b "Milestone B" {
milestone
start 2013-01-01
}
}
}
taskreport "Gantt Chart" {
headline "Project Gantt Chart"
columns hierarchindex, name, start, end, effort, duration, completed,
chart
timeformat "%Y-%m-%d"
hideresource 1
loadunit shortauto
}
resourcereport "Resource Graph" {
headline "Resource Allocation Graph"
columns no, name, utilization, freeload, chart
loadunit shortauto
sorttasks startup
hidetask ~isleaf()
}
--
Johnny
next reply other threads:[~2011-11-03 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 16:19 Johnny [this message]
2011-11-07 16:27 ` org-taskjuggler export problems Christian Egli
2011-11-07 17:02 ` Johnny
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=8739e5kwk6.fsf@gmx.co.uk \
--to=yggdrasil@gmx.co.uk \
--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).