ox-taskjuggler: no multiple vacation / leaves entries

ox-taskjuggler: no multiple vacation / leaves entries

[Axel Kielhorn]

[-- Attachment #1: Type: text/plain, Size: 724 bytes --]

Hi!

I’ve been looking for project management tools that can handle local or even company wide holidays.
So far Taskjuggler looks fine but there are some minor deficiencies in the org interface.

In the enclosed org file I have two vacations, but only the last one is exported.
Of cause I could write all vacations in one line but that is difficult to read and edit.

The same happens with leaves[1]:
The first MA has two holidays, while the second has 4. But only 2 days are exported to taskjuggler.

Is there a way to make these keywords cumulative?
Taskjuggler handles multiple leaves/vacation lines.

Axel

[1] After adding the „leaves“ keyword to org-taskjuggler-valid-resource-attributes.




[-- Attachment #2: ECM-taskjuggler.org --]
[-- Type: application/octet-stream, Size: 1308 bytes --]

#+TAGS: taskjuggler_project taskjuggler_resource
#+PROPERTY: Effort_ALL 0 1d 2d 5d 2w 3w 4w 50:00 100:00 200:00
#+PROPERTY: allocate_ALL KB MA1 MA2


* Testprojekt                                           :taskjuggler_project:
   :PROPERTIES:
   :COLUMNS:  %32ITEM(Aufgabe) %10ID %8allocate(Wer) %12effort %12duration %BLOCKER %12TAGS
   :task_id:  beutel
   :END:
** Konstruktion
:PROPERTIES:
:ID:       MKB
:END:

*** Aufgabe 1
:PROPERTIES:
:ALLOCATE: MA1
:EFFORT:   4w
:ID:       T1
:END:
*** Aufgabe 2
:PROPERTIES:
:ALLOCATE: MA1
:EFFORT:   4w
:ID:       T2
:END:
*** Aufgabe 3
:PROPERTIES:
:ALLOCATE: MA2
:EFFORT:   4w
:ID:       T3
:END:
* Mitarbeiter                                          :taskjuggler_resource:
:PROPERTIES:
:COLUMNS:  %40ITEM %8resource_id(Name) %rate %efficiency %leaves
:END:      
** KB
:PROPERTIES:
:resource_id: KB
:vacation: "Deutsche_Einheit" 2016-10-03
:vacation: "50 jähriges Jubiläum" 2016-09-01
:END:

*** MA1
:PROPERTIES:
:resource_id: MA1
:leaves: holiday 2016-06-27, holiday 2016-08-12 
:EFFICIENCY: 0.80
:RATE:     250
:END:
*** MA2
:PROPERTIES:
:resource_id: MA2
:leaves: holiday 2016-06-27, holiday 2016-08-12 
:leaves: holiday 2016-07-27, holiday 2016-07-12 
:EFFICIENCY: 0.70
:RATE:     250
:END:


[-- Attachment #3: ECM-taskjuggler.tjp --]
[-- Type: application/octet-stream, Size: 1617 bytes --]

project nil "Testprojekt" "1.0" 2016-06-27 +280d {
}
shift s40 "Part time shift" {
  workinghours wed, thu, fri off
}
resource KB "KB" {
  vacation "50 jähriges Jubiläum" 2016-09-01
  resource MA1 "MA1" {
    leaves holiday 2016-06-27, holiday 2016-08-12
    efficiency 0.80
    rate 250
  }
  resource MA2 "MA2" {
    leaves holiday 2016-07-27, holiday 2016-07-12
    efficiency 0.70
    rate 250
  }
}
task beutel "Testprojekt" {
  task konstruktion "Konstruktion" {
    task aufgabe "Aufgabe 1" {
      purge allocate
      allocate MA1
      effort 160.0h
    }
    task aufgabe__2 "Aufgabe 2" {
      purge allocate
      allocate MA1
      effort 160.0h
    }
    task aufgabe__3 "Aufgabe 3" {
      purge allocate
      allocate MA2
      effort 160.0h
    }
  }
}
textreport report "Plan" {
  formats html
  header '== Testprojekt =='

  center -8<-
    [#Plan Plan] | [#Resource_Allocation Resource Allocation]
    ----
    === Plan ===
    <[report id="plan"]>
    ----
    === Resource Allocation ===
    <[report id="resourceGraph"]>
  ->8-
}

# A traditional Gantt chart with a project overview.
taskreport plan "" {
  headline "Project Plan"
  columns bsi, name, start, end, effort, chart
  loadunit shortauto
  hideresource 1
}

# A graph showing resource allocation. It identifies whether each
# resource is under- or over-allocated for.
resourcereport resourceGraph "" {
  headline "Resource Allocation Graph"
  columns no, name, effort, weekly
  loadunit shortauto
  hidetask ~(isleaf() & isleaf_())
  sorttasks plan.start.up
}