From: "Søren Mikkelsen" <firstname.lastname@example.org>
Subject: Re: [bug] ox-taskjuggler
Date: Wed, 21 Jan 2015 14:08:46 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
On 2015-01-20 22:00, Nicolas Goaziou wrote:
> Søren Mikkelsen <firstname.lastname@example.org> writes:
>> I'm trying to use the taskjuggler exporter for getting an overview of my
>> project, and it seems to be straight forward if you know a bit about
>> However, tasks that are scheduled org-mode like, i.e.,
>> *** TODO My task
>> SCHEDULED: <2015-01-27 Tue>
>> don't appear in the report. But, if I add a START property it will appear.
>> *** TODO My task 2
>> :start: 2015-03-01
>> I suspect it has something to do with l462-470:
>> (defun org-taskjuggler-get-start (item)
>> "Return start date for task or resource ITEM.
>> ITEM is a headline. Return value is a string or nil if ITEM
>> doesn't have any start date defined."
>> (let ((scheduled (org-element-property :scheduled item)))
>> (and scheduled (org-timestamp-format scheduled "%Y-%02m-%02d"))
>> (and (memq 'start org-taskjuggler-valid-task-attributes)
>> (org-element-property :START item)))))
>> I'm not that experienced in elisp, so I hope someone can help me.
> There is no bug in the snippet shown.
> "ox-taskjuggler" just doesn't use SCHEDULED to set start property for
> tasks. However, it will use SCHEDULED to set the start date for the
> Note that I don't use Taskjuggler, so I don't know if this is the right
> behaviour or not.
According to the org mode docs, assigning the start of a task should be
possible both ways:
Or am I misinterpreting the docs?
next prev parent reply other threads:[~2015-01-21 13:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 12:44 [bug] ox-taskjuggler Søren Mikkelsen
2015-01-20 21:00 ` Nicolas Goaziou
2015-01-21 13:08 ` Søren Mikkelsen [this message]
2015-01-21 13:31 ` John Hendy
2015-01-22 7:26 ` Søren Mikkelsen
2015-01-22 10:21 ` Christian Egli
2015-01-22 11:55 ` Søren Mikkelsen
2015-01-23 8:59 ` Christian Egli
2015-01-23 11:31 ` Søren Mikkelsen
2015-01-26 12:30 ` Christian Egli
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 \
* 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).