emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Søren Mikkelsen" <soren@aamikkelsen.dk>
To: emacs-orgmode@gnu.org
Subject: Re: [bug] ox-taskjuggler
Date: Thu, 22 Jan 2015 08:26:22 +0100	[thread overview]
Message-ID: <m9q8mu$gdo$1@ger.gmane.org> (raw)
In-Reply-To: <CA+M2ft8jmCK_i1eaStj9ZkG-re6s3D3srqbpwprhH2AizqndKQ@mail.gmail.com>

Hash: SHA1

On 2015-01-21 14:31, John Hendy wrote:
> On Jan 21, 2015 7:09 AM, "Søren Mikkelsen" <soren@aamikkelsen.dk 
> <mailto:soren@aamikkelsen.dk>> wrote:
>> On 2015-01-20 22:00, Nicolas Goaziou wrote:
>>> Hello,
>>> Søren Mikkelsen <smik@iha.dk <mailto:smik@iha.dk>> 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 Taskjuggler.
>>>> 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 :PROPERTIES: :start:    2015-03-01 :END:
>>>> 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))) (or (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 project.
>>> Note that I don't use Taskjuggler, so I don't know if this is
>>> the right behaviour or not.
>>> Regards,
>> According to the org mode docs, assigning the start of a task
>> should be possible both ways:
>> http://orgmode.org/worg/exporters/taskjuggler/ox-taskjuggler.html#sec-5
Or am I misinterpreting the docs?
> Well, I wrote that , so you may be correctly interpreting docs
> written by someone who misunderstood!
> Perhaps the SCHUDULED property is just for the main project
> container. I don't see it actually used in any examples?
No, not other than the task example I was referring to.
> Sorry if the confusion was my fault! John
>> -- Best regards, Søren Mikkelsen
It would, however, make sense to be able to scheduled tasks where
interpreted as the start time, if the org-file is used for more than
just generating the report.

- -- 
Best regards,
Søren Mikkelsen
Version: GnuPG v1


  reply	other threads:[~2015-01-22  7:26 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
2015-01-21 13:31     ` John Hendy
2015-01-22  7:26       ` Søren Mikkelsen [this message]
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

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='m9q8mu$gdo$1@ger.gmane.org' \
    --to=soren@aamikkelsen.dk \
    --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).