jtt fetch#
List the issues touched in a period, with the tracked field’s current value.

$ jtt fetch --from 2026-09-21 --to 2026-09-28
$ jtt fetch -p OPS --from 2026-09-21 --to 2026-09-28 --user me
These are the issues jtt calculate examines: updated since the period
started, and created before it ended. fetch stops there, without reading change histories,
so it is quick, and the values are today’s, not what changed in the period.
With --user, only the issues that person held at some point in the period. --json prints
the query and Jira’s raw answer instead of a table, for a script:
$ jtt fetch --from 2026-09-21 --to 2026-09-28 --json
Options#
jtt fetch [OPTIONS]
Option |
Default |
Description |
|---|---|---|
|
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. |
|
|
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. |
|
|
Print raw JSON instead of a table. |
|
|
Show the command’s help and exit. |