Re: [O] [bug] ox-taskjuggler

Søren Mikkelsen writes: > On 2015-01-23 09:59, Christian Egli wrote: >> Søren Mikkelsen writes: >> >>> It works, but only for tasks that aren't having a start >>> attribute. It is possible to give a warning if the start >>> attribute already exists and make the default one, the one >>> specifie

Re: [O] [bug] ox-taskjuggler

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2015-01-23 09:59, Christian Egli wrote: > Søren Mikkelsen writes: > >> It works, but only for tasks that aren't having a start >> attribute. It is possible to give a warning if the start >> attribute already exists and make the default one, the on

Re: [O] [bug] ox-taskjuggler

Søren Mikkelsen writes: > It works, but only for tasks that aren't having a start attribute. It > is possible to give a warning if the start attribute already exists > and make the default one, the one specified in the attributes (drawer)? What exactly doesn't work? Are there two start entries i

Re: [O] [bug] ox-taskjuggler

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2015-01-22 11:21, Christian Egli wrote: > Søren Mikkelsen writes: > >> 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. > > I

Re: [O] [bug] ox-taskjuggler

Søren Mikkelsen writes: > 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. I agree that it would make sense to use the scheduled date as the start time. The same is probably true

Re: [O] [bug] ox-taskjuggler

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2015-01-21 14:31, John Hendy wrote: > > On Jan 21, 2015 7:09 AM, "Søren Mikkelsen" > wrote: >> >> On 2015-01-20 22:00, Nicolas Goaziou wrote: >>> Hello, >>> >>> Søren Mikkelsen mailto:s...@iha.dk>> writes: >>>

Re: [O] [bug] ox-taskjuggler

On Jan 21, 2015 7:09 AM, "Søren Mikkelsen" wrote: > > On 2015-01-20 22:00, Nicolas Goaziou wrote: > > Hello, > > > > Søren Mikkelsen 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

Re: [O] [bug] ox-taskjuggler

On 2015-01-20 22:00, Nicolas Goaziou wrote: > Hello, > > Søren Mikkelsen 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

Re: [O] [bug] ox-taskjuggler

Hello, Søren Mikkelsen 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-

[O] [bug] ox-taskjuggler

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 a

Re: [O] [BUG] ox-taskjuggler: unable to use depends {gapduration}

Christian Egli writes: > OK, the fix is pushed to maint and merged to master. Thank you. As a side note, two spaces after sentences are required in commit messages. Regards,

Re: [O] [BUG] ox-taskjuggler: unable to use depends {gapduration}

Nicolas Goaziou writes: >> Nicolas, I can push this myself but I haven't pushed to the repo in >> years. What is the current way? Do I just push to master? > > I think you should push to maint, so that users of org+contrib package > can benefit from your fix soon enough. You then need to merge m

Re: [O] [BUG] ox-taskjuggler: unable to use depends {gapduration}

On Wed, Nov 5, 2014 at 2:21 AM, Christian Egli wrote: > John Hendy writes: > >> I ran into an odd issue with a taskjuggler task tree I'm working on >> when trying to apply a gapduration attribute to a task dependency. >> Typically, I can just pass any valid taskjuggler attribute through >> using

Re: [O] [BUG] ox-taskjuggler: unable to use depends {gapduration}

Hello, Christian Egli writes: > No it is indeed a bug. At first I thought this was simply no longer > working in the new exporter but I was wrong. Nicolas of course > implemented it and way more. But there is a subtle bug. I actually found > it because I wondered about the funny "t :taskjuggl" i

Re: [O] [BUG] ox-taskjuggler: unable to use depends {gapduration}

John Hendy writes: > I ran into an odd issue with a taskjuggler task tree I'm working on > when trying to apply a gapduration attribute to a task dependency. > Typically, I can just pass any valid taskjuggler attribute through > using properties, but my export was producing an error when trying t

[O] [BUG] ox-taskjuggler: unable to use depends {gapduration}

I ran into an odd issue with a taskjuggler task tree I'm working on when trying to apply a gapduration attribute to a task dependency. Typically, I can just pass any valid taskjuggler attribute through using properties, but my export was producing an error when trying to use: :depends: task {gapdu

Re: [O] Bug: ox-taskjuggler :effort: property incorrectly converted when in minutes

On Sun, Nov 2, 2014 at 5:25 PM, Nicolas Goaziou wrote: > John Hendy writes: > >> Thanks for the explanation. I pretty much only use duration, which has >> never had an issue. As a fluke I used effort and noticed the big >> difference. Thanks for illuminating the situation! > > Actually, I was sli

Re: [O] Bug: ox-taskjuggler :effort: property incorrectly converted when in minutes

John Hendy writes: > Thanks for the explanation. I pretty much only use duration, which has > never had an issue. As a fluke I used effort and noticed the big > difference. Thanks for illuminating the situation! Actually, I was slightly wrong. According to `org-duration-string-to-minutes' and `o

Re: [O] Bug: ox-taskjuggler :effort: property incorrectly converted when in minutes

On Sun, Nov 2, 2014 at 5:01 PM, Nicolas Goaziou wrote: > John Hendy writes: > >> That mostly makes sense. Org's not case-sensitive, correct? > > Correct. > >> I was looking at the [granted, outdated] taskjuggler documentation and >> it features estimates in days (i.e. 10d): - >> http://orgmode.or

Re: [O] Bug: ox-taskjuggler :effort: property incorrectly converted when in minutes

John Hendy writes: > That mostly makes sense. Org's not case-sensitive, correct? Correct. > I was looking at the [granted, outdated] taskjuggler documentation and > it features estimates in days (i.e. 10d): - > http://orgmode.org/worg/org-tutorials/org-taskjuggler.html > > Is this recent (as in

Re: [O] Bug: ox-taskjuggler :effort: property incorrectly converted when in minutes

On Sun, Nov 2, 2014 at 4:47 PM, Nicolas Goaziou wrote: > Hello, > > John Hendy 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

Re: [O] Bug: ox-taskjuggler :effort: property incorrectly converted when in minutes

Hello, John Hendy 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

[O] Bug: ox-taskjuggler :effort: property incorrectly converted when in minutes

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

[O] Bug: ox-taskjuggler ignores SCHEDULED attribute [8.2.6 (8.2.6-47-ge3d2c1-elpa @ /home/anakreontas/.emacs.d/elpa/org-20140526/)]

When exporting the attached file to task juggler, the SCHEDULED attribute is not included in the generated file as a "start" attribute. The export process is invoked with the key sequence C-c C-e J j * Project A :taskjuggler_project: :PROPERTIES: