jtt export#
Write a report to a file: CSV, JSON or Markdown.

$ jtt export -k contributions -o september.csv --from 2026-09-01 --to 2026-10-01
$ jtt export -k issues -o week.json --from 2026-09-21 --to 2026-09-28
$ jtt export -k daily -o week.md --from 2026-09-21 --to 2026-09-28
The file’s extension picks the format, or --format does. CSV is written with a byte order
mark, so Excel opens accented names correctly; JSON and Markdown also carry the report’s
settings: the project, field, unit, period, person and query.
--kind chooses what each row is:
issues(the default)One row per issue touched in the period: its value now, the value it was created with, its changes in the period and its net, as in
calculate.changesOne row per change in the period, with its time, author, the person holding the issue, and the value before and after.
contributionsOne row per person, as in
contributions.dailyOne row per day of the period, with its net.
--user and --attribution work as in calculate. An existing file is kept
unless you pass --force:
$ jtt export -k contributions -o september.csv --from 2026-09-01 --to 2026-10-01 --force
Options#
jtt export [OPTIONS]
Option |
Default |
Description |
|---|---|---|
|
required |
File to write; the extension picks the format. |
|
|
What each row is. |
|
Override the format. |
|
|
Project key; defaults to the one set by init. |
|
|
First day, included (YYYY-MM-DD). |
|
|
Last bound, excluded (YYYY-MM-DD). Defaults to tomorrow, so today counts. |
|
|
Named period instead of –from/–to: today, yesterday, this-week, last-week, this-month, last-month, this-quarter, last-quarter, this-year, last-7-days, last-30-days. |
|
|
Account id, ‘me’, or part of a name or email. |
|
|
|
As in calculate. |
|
Show time amounts in another time unit. |
|
|
Leave out issues that have subtasks or child issues, so work estimated on both a story and its subtasks is counted once. |
|
|
|
Parallel changelog requests. From 1 to 32. |
|
Overwrite an existing file. |
|
|
Show the command’s help and exit. |