From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Bug: ox-taskjuggler :effort: property incorrectly converted when in minutes
Date: Sun, 02 Nov 2014 23:47:32 +0100 [thread overview]
Message-ID: <878ujtgqyj.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CA+M2ft8Jf3o3Gd2AYeKARV8W1aDRwAawq9vMTgip1oNkJmzbZw@mail.gmail.com> (John Hendy's message of "Sun, 2 Nov 2014 16:26:45 -0600")
Hello,
John Hendy <jw.hendy@gmail.com> writes:
> I ran into an error with a 30min task which used the :effort: property
> to set this duration. Upon compilation, I noted the warning:
> ```
> file.tjp:10: Warning: 400.0d of effort of task one does not fit into
> the project time frame.
> Warning: 1 tasks could not be scheduled
> ```
>
> I looked at the .tjp file, and 30min had been converted to 4800.0
> hours. I was able to reproduce with the following setup:
>
> #+begin_src min-config
> (add-to-list 'load-path "~/.elisp/org.git/contrib/lisp/")
> (require 'ox-taskjuggler)
> #+end_src
>
> emacs -Q M-x load-file ~/path/to/min-config
>
> #+begin_src tj-time-test.org
>
> * Project :taskjuggler_project:
> ** task1-effort-min
> :PROPERTIES:
> :start: 2014-11-01
> :effort: 30min
> :allocate: jwhendy
> :END:
> ** task2-duration-min
> :PROPERTIES:
> :duration: 30min
> :allocate: jwhendy
> :blocker: previous-sibling
> :END:
>
> #+end_src
>
EFFORT is a special property in Org (i.e., it is not specific to
taskjuggler). It expects "HH:MM" format. So, you should set it to
:Effort: 00:30
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-11-02 22:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 22:26 Bug: ox-taskjuggler :effort: property incorrectly converted when in minutes John Hendy
2014-11-02 22:47 ` Nicolas Goaziou [this message]
2014-11-02 22:54 ` John Hendy
2014-11-02 23:01 ` Nicolas Goaziou
2014-11-02 23:07 ` John Hendy
2014-11-02 23:25 ` Nicolas Goaziou
2014-11-03 21:53 ` John Hendy
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=878ujtgqyj.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@gmail.com \
/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).