From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Garber Subject: ox taskjuggler issues: (1) unable to set 'timingresolution' (2) taskjuggler_resource not found (3) property/attribute aliases Date: Thu, 19 Jun 2014 14:14:23 -0400 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e011615fc7ac3e404fc345a52 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57791) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WxgrP-00048M-HU for emacs-orgmode@gnu.org; Thu, 19 Jun 2014 14:14:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WxgrO-0002ne-A2 for emacs-orgmode@gnu.org; Thu, 19 Jun 2014 14:14:55 -0400 Received: from mail-yh0-x230.google.com ([2607:f8b0:4002:c01::230]:61928) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WxgrO-0002nT-48 for emacs-orgmode@gnu.org; Thu, 19 Jun 2014 14:14:54 -0400 Received: by mail-yh0-f48.google.com with SMTP id b6so2019257yha.35 for ; Thu, 19 Jun 2014 11:14:53 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org --089e011615fc7ac3e404fc345a52 Content-Type: text/plain; charset=UTF-8 Hello, In exploring the use of OrgMode for advanced project planning I've run across a few questions/problems with the taskjuggler exporter that I'd like to raise. (1) unable to set 'timingresolution' My project contains some short tasks, such as brief but required meetings, that are less than the default timing resolution of 60 mins and so causes the Taskjuggler export-and-process to fail with EM: "TaskJuggler failed with errors: Error: Effort value must at least as large as the timing resolution (60min)." I'd like to set the default value for the attribute to "5 min", the minimum value, but apparently a facility for this is not provided via orgmode. What I'm doing so far is creating the .tjp file, editing in this value, then exporting with =tj3 somefile.tjp= from the command line, and this _does_ work, but is awkward and hopefully avoidable. This might be most sensibly resolved by adding an, 'Org Export Taskjuggler Default Project Attributes' variable to those available via M-x customize-group org-export-taskjuggler . (2) taskjuggler_resource not found When specifying the OrgMode heading where the project resources will live with the :taskjuggler_resource: tag, I've found that this tag is not exported unless it is attached to a top level headline. To work around this I've moved the project's tree from it's main .org file, in order to promote the "* Project Resource Info" headline without disrupting my normal and thus precious ;-) headline "schema". I didn't see "attach to first-level headline" described as a resource export requirement and thought it unusual enough to mention in case it is not an intended limitation. (3) property/attribute aliases This is a question about a capability, or perhaps a feature request if the capability doesn't already exist. The way that OrgMode uses properties and TaskJuggler uses attributes is generally very compatible! I wonder though if its currently (or could be made) possible to specify a conversion relationship between properties and attributes on taskjuggler export. Using myself as an example: - I have a :WorkedBy: property for all my tasks that indicates the person(s) with responsibility for performing the work of a task. - The "allocate" attribute, used to assign resourced to tasks, is created on export from the :allocate: property. - The purpose and concept of :WorkedBy: maps well to Taskjuggler's "allocate" attribute, but not as well in reverse, which discourages replacing :WorkedBy: with "allocate" globally. - So for now I'm using both WorkedBy and allocate side-by-side, which is mostly redundant. It'd be grand to be able to specify only :WorkedBy: and have that value automatically renamed (a/o prepended) to :allocate: on export. Or perhaps there is a way to do this using computed properties, (which I likely insufficiently understand) ? To Conclude: My hope is to use this to replace our dependence on MS Project at work and further extend the power and reach of OrgMode in all the things. Cheers and many thanks! -- Nick Garber --089e011615fc7ac3e404fc345a52 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

In exploring = the use of OrgMode for advanced project planning I've run across a few = questions/problems with the taskjuggler exporter that I'd like to raise= .


(1) unable to set 'timingresolution'

My = project contains some short tasks, such as brief but required meetings, tha= t are less than the default timing resolution of 60 mins and so causes the = Taskjuggler export-and-process to fail with EM:
"TaskJuggler failed with errors: Error: Effort value must a= t least as large as the timing resolution (60min)."

= I'd like to set the default value for the attribute to "5 min"= ;, the minimum value, but apparently a facility for this is not provided vi= a orgmode.

What I'm doing so far is creating the .tjp file, editin= g in this value, then exporting with =3Dtj3 somefile.tjp=3D from the comman= d line, and this _does_ work, but is awkward and hopefully avoidable.

This might be most sensibly resolved by adding an, '= ;Org Export Taskjuggler Default Project Attributes' variable to those a= vailable via M-x customize-group org-export-taskjuggler=C2=A0 .


(2) taskjuggler_resource not found
<= div>
When specifying the OrgMode heading where the project resources wil= l live with the :taskjuggler_resource: tag, I've found that this tag is= not exported unless it is attached to a top level headline.

To work around this I've moved the project's tree fr= om it's main .org file, in order to promote the "* Project Resourc= e Info" headline without disrupting my normal and thus precious ;-) he= adline "schema".
I didn't see "attach to first-level headline" desc= ribed as a resource export requirement and thought it unusual enough to men= tion in case it is not an intended limitation.


(3) pr= operty/attribute aliases

This is a question about a capability, or perhaps a feature = request if the capability doesn't already exist.
The way= that OrgMode uses properties and TaskJuggler uses attributes is generally = very compatible! I wonder though if its currently (or could be made) possib= le to specify a conversion relationship between properties and attributes o= n taskjuggler export.

Using myself as an example:
=C2=A0- I have a := WorkedBy: property for all my tasks that indicates the person(s) with respo= nsibility for performing the work of a task.
=C2=A0- The= "allocate" attribute, used to assign resourced to tasks, is crea= ted on export from the :allocate: property.
=C2=A0- The purpose and concept of :WorkedBy: maps well to Taskjuggle= r's "allocate" attribute, but not as well in reverse, which d= iscourages replacing :WorkedBy: with "allocate" globally.
=C2=A0- So for now I'm using both WorkedBy and allocate side-by-side, w= hich is mostly redundant.

It'd be grand to be able to specify only :WorkedBy:= and have that value automatically renamed (a/o prepended) to :allocate: on= export.
Or perhaps there is a way to do this using computed properties= , (which I likely insufficiently understand) ?



To Conclude:
My hope is to use this to replace our dependenc= e on MS Project at work and further extend the power and reach of OrgMode i= n all the things.

Cheers and many thanks!

--
Nick Garber
--089e011615fc7ac3e404fc345a52--