emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* More generic taskjuggler export proposal
@ 2013-04-03 20:25 Buddy Butterfly
  2013-04-12 13:08 ` Christian Egli
  0 siblings, 1 reply; 3+ messages in thread
From: Buddy Butterfly @ 2013-04-03 20:25 UTC (permalink / raw)
  To: emacs-orgmode


I would like propose the following for taskjuggler export
as base for a discussion to change export functionality.
Here I will refer to the example project of taskjuggler 3.

- Functionality of tj should be kept in tj as much as possible
- org export should be as generic as possible such that changes
  in tj will not impact org.

- There should be configurable global taskjuggler prefix to define
  what shoudl be exported. Here we will take "tj_" as an example.

- tj elements of the form
  : <keyword> <id> <name> { <attributes> }
  should be implemented as tagged tasks (like already done for resources
and project).
  The org tag should be prefixed by the tj prefix and the tag name
should automatically
  be exported as the <keyword> of tj. Org task should go into tj <name>
and the org
  property tj_id should go into <id>.

  The attributes should be org properties prefixed by the prefix (here
  Example for the project tag:

  The tj example project lists the following project keyword header:

  project your_project_id "Your Project Title"  2011-11-11-0:00--0500 +4m {
    timezone "America/New_York"
    timeformat "%Y-%m-%d"
    numberformat "-" "" "," "." 1
    currencyformat "(" ")" "," "." 0
    now 2011-12-24
    currency "USD"

    # You can define multiple scenarios here if you need them.
    #scenario plan "Plan" {
    #  scenario actual "Actual"

    # You can define your own attributes for tasks and resources. This
    # is handy to capture additonal information about the project that
    # is not directly impacting the project schedule but you like to
    # keep in one place.
    #extend task {
    #  reference spec "Link to Wiki page"
    #extend resource {
    #  text Phone "Phone"

  This would be written in org like

  * Your Project Title                                         :tj_project:
    :tj_id: your_project_id
    :tj_timezone: "America/New_York"
    :tj_timeformat: "%Y-%m-%d"
    :tj_numberformat:  "-" "" "," "." 1
    :tj_currencyformat: "(" ")" "," "." 0
    :tj_now: 2011-12-24
    :tj_currency: "USD"

    * Plan                                               :tj_scenario:
      :tj_scenario: actual "Actual"

    * task                                               :tj_extend:
      :tj_reference: spec "Link to Wiki page"

    * resource                                           :tj_extend:
      :tj_text: Phone "Phone"

  As we can see, org can export everything in a generic way with mainly
  the prefix "tj_" from the tags and properties and export as is to
  This also maps to the well known resource mapping:

  # This is a set of example resources.
  resource r1 "Resource 1"
  resource t1 "Team 1" {
    managers r1
    resource r2 "Resource 2"
    resource r3 "Resource 3"

  # This is a resource that does not do any work.
  resource s1 "System 1" {
    efficiency 0.0
    rate 600.0

  Would be written in org-mode like:

  * Resource 1                                             :tj_resource:
    :tj_id: r1

  * Team 1                                             :tj_resource:
    :tj_id: t1
    :tj_managers: r1
    * Resource 2
      :tj_id: r2

    * Resource 3
      :tj_id: r3

  * System 1                                             :tj_resource:
    :tj_id: s1
    :tj_efficiency: 0.0
    :tj_rate: 600.0

 Here the fact of inheritance of org tags have been taken into account in
 org task "Team 1" for resource "Resource 2" and "Resource 3".

 For the tasks the same holds:

 task project "Project" {
  task wp1 "Workpackage 1" {
    task t1 "Task 1"
    task t2 "Task 2"
  task wp2 "Work package 2" {
    depends !wp1
    task t1 "Task 1"
    task t2 "Task 2"
  task deliveries "Deliveries" {
    task "Item 1" {
      depends !!wp1
    task "Item 2" {
      depends !!wp2

  Org mode:

  * Project                                              :tj_task:
    :tj_id: project

    * Workpackage 2
      :tj_id: wp2

      * Task 1
        :tj_id: t1
        :tj_depends: !wp1
      * Task 2
        :tj_id: t2

Also accounts could be easily generated with this

account cost "Project Cost" {
  account dev "Development"
  account doc "Documentation"


 * Project Cost                      :tj_account:
   :tj_id: cost

   * Development
     :tj_id: dev
   * Documentation
     :tj_id: doc

 There is still the question how to implement properties that go into
 the global part of a tj file. Here I would suggest that one can place
 this data inbetween

 # The Profit&Loss analysis should be rev - cost accounts.
 balance cost rev

 # Define you public holidays here.
 vacation "New Year's Day" 2012-01-02
 vacation "Birthday of Martin Luther King, Jr." 2012-01-16
 vacation "Washington's Birthday" 2012-02-20
 vacation "Memorial Day" 2012-05-28
 vacation "Independence Day" 2012-07-04
 vacation "Labor Day" 2012-09-03
 vacation "Columbus Day" 2012-10-08
 vacation "Veterans Day" 2012-11-12
 vacation "Thanksgiving Day" 2012-11-22
 vacation "Christmas Day" 2012-12-25

 # The daily default rate of all resources. This can be overridden for each
 # resource. We specify this, so that we can do a good calculation of
 # the costs of the project.
 rate 400.0

 The dependency between tasks is one thing that should be supported by org.
 I do not know what would be the best solution here. Maybe we could get
 a completion list for the values when adding :tj_depends: properties.

This is all for now. I still would like to discuss the organisation with
multiple projects. What do you think about it?

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-04-14 12:51 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-04-03 20:25 More generic taskjuggler export proposal Buddy Butterfly
2013-04-12 13:08 ` Christian Egli
2013-04-14 12:51   ` Suvayu Ali

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).