From: John Hendy <jw.hendy@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Bug: ox-taskjuggler :effort: property incorrectly converted when in minutes
Date: Sun, 2 Nov 2014 16:26:45 -0600 [thread overview]
Message-ID: <CA+M2ft8Jf3o3Gd2AYeKARV8W1aDRwAawq9vMTgip1oNkJmzbZw@mail.gmail.com> (raw)
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
Exported this via =C-e J j=; report section omitted below.
#+begin_src tj-time-test.tjp
project nil "Project" "1.0" 2014-11-02 +280d {
}
shift s40 "Part time shift" {
workinghours wed, thu, fri off
}
resource jwhendy "" {
}
task project "Project" {
task task1_effort_min "task1-effort-min" {
purge allocate
allocate jwhendy
effort 4800.0h
start 2014-11-01
}
task task2_duration_min "task2-duration-min" {
depends !task1_effort_min
purge allocate
allocate jwhendy
duration 30min
}
}
#+end_src
Note the effort vs. duration time processing.
I tried the property :Effort: instead, as that's used in Worg and I
wondered if it was "built-in" (even though any tj attribute should be
able to be passed through a property) and got the same result.
From what I can tell, effort/duration/length all have the same
definition structure:
- http://www.taskjuggler.org/tj3/manual/effort.html
- http://www.taskjuggler.org/tj3/manual/duration.html
Thanks for any feedback or requests for more info.
John
next reply other threads:[~2014-11-02 22:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 22:26 John Hendy [this message]
2014-11-02 22:47 ` Bug: ox-taskjuggler :effort: property incorrectly converted when in minutes Nicolas Goaziou
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=CA+M2ft8Jf3o3Gd2AYeKARV8W1aDRwAawq9vMTgip1oNkJmzbZw@mail.gmail.com \
--to=jw.hendy@gmail.com \
--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).