New feature: export

[stefanoco]

Export

So that I can include an estimate in a document for my client, and convert an estimate to a plan.

• easy: plain fixed fields CSV
• more: configurable fields CSV, JSON, XML, taskjuggler file format (http://www.taskjuggler.org/)
• import: also very useful

[geon]

Sounds very useful. Could you type in an example of what a CSV might look like? What should it include to be most useful?

[stefanoco]

CSV Format

The usual format for CSV should look something like this:

"fieldname1","fieldname2","fieldname3","fieldname4",...
"field1","field2","field3","field4",...
"field1","field2","field3","field4",...
"field1","field2","field3","field4",...

I'm not sure but I think having "" around each field is a good idea.

CSV content

The first row should contain only fields names; the next rows can be one task / subtask for each row. Not important the order in my opinion, tasks should be linked each other by means of the fields themselves.

In order for the tasks to be linked each other the correct way I need two details:

• who is my parent task? (the task that I'm smaller part of, on the left in the web panel)
• who is my previous task? (the task that I'm coming after of, on the up in the web panel)

Fields

Fields important to have:

• unique id
• parent unique id
• previous unique id
• task full name
• task description text
• task colour code (HTML RGB standard format?)
• min estimate as input
• max estimate as input
• min estimate as calculated
• max estimate as calculated
• actual estimate as input