### The TaskJuggler User Manual

Project Management beyond Gantt Chart Drawing

<< epilog << | Table Of Contents | >> extend >>

Keyword | export

Purpose

The export report looks like a regular TaskJuggler file with the provided input data complemented by the results of the scheduling process. The content of the report can be controlled with the definitions attribute. In case the file contains the project header, a `.tjp` extension is added to the file name. Otherwise, a `.tji` extension is used.

The resourceattributes and taskattributes attributes provide even more control over the content of the file.

The export report can be used to share certain tasks or milestones with other projects or to save past resource allocations as immutable part for future scheduling runs. When an export report is included the project IDs of the included tasks must be declared first with the project id property.

Syntax | `export [<id>] <file name> [{ <attributes> }]`
Arguments | id [ID] | An optional ID. If you ever want to reference this property, you must specify your own unique ID. If no ID is specified one will be automatically generated. These IDs may become visible in reports, but may change at any time. You may never rely on automatically generated IDs.
file name [STRING] | The name of the report file to generate. It must end with a .tjp or .tji extension, or use . to use the standard output channel.
Context | accountreport, export, properties, resourcereport, taskreport, textreport, tracereport

Attributes | Name | Scen. spec. | Inh. fm. Global | Inh. fm. Parent
accountreport |  |  |
definitions |  |  |
end (report) |  | x | x
export |  |  |
formats (export) |  |  |
hideresource |  |  |
hidetask |  |  |
loadunit |  |  |
period (report) |  |  |
purge |  |  |
resourceattributes |  |  |
resourcereport |  |  |
rollupresource |  |  |
rolluptask |  |  |
scenarios (export) |  |  |
start (report) |  | x | x
taskattributes |  |  |
taskreport |  |  |
taskroot (export) |  |  |
textreport |  |  |
timezone (export) |  |  |
tracereport |  |  |

    project export  "Project" "1.0" 2007-01-01 - 2008-01-01 {
      timezone "America/Denver"
    }

    resource tux "Tux"
    resource bob "Bob"

    task t1 "Task 1" {
      start 2007-01-01
      effort 20d
      allocate tux
      allocate bob
      limits { dailymax 6h }
    }
    task t2 "Task 2" {
      start 2007-01-01
      end 2007-06-30
      allocate tux
      allocate bob
      limits { weeklymax 3d }
    }

    # Export the project as fully scheduled project.
    export "FullProject" {
      definitions *
      taskattributes *
      hideresource 0
    }

    # Export only bookings for 1st week as resource supplements
    export "Week1Bookings" {
      definitions -
      start 2007-01-01
      end 2007-01-08
      taskattributes booking
      hideresource 0
    }

    # Export the scheduled project as Microsoft Project XML format.
    export "MS-Project" {
      formats mspxml
      loadunit quarters
    }

<< epilog << | Table Of Contents | >> extend >>

Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012 by Chris Schlaeger <chris@linux.com>.TaskJuggler is a trademark of Chris Schlaeger.