Commands

Every command prints its options with -h: jtt calculate -h. Each page below shows the command running, against the simulated Jira site.

Command	What it does
login	Check an API token with Jira and store it securely
logout	Remove the stored token; --purge also forgets the project settings
whoami	The logged-in account, where the token is kept, and the configured projects
init	Choose, per project, the field that holds the estimate, and its unit
fields	A project’s numeric fields, optionally with how many issues hold a value
projects	The projects you can see, and what each one tracks
config show	Every setting
config path	Where the settings file is
config default	The project used when -p is left out
config set	Change a project’s field or units without init
config remove	Forget a project’s settings
config calendar	The working day and week used to convert time units
fetch	The issues touched in a period, with their current value
calculate	The net amount that came into being in a period, per issue
contributions	The net per person, with statistics and a daily or weekly breakdown
collaborators	Who can be assigned in a project, with their current load
export	Issues, changes, contributions or a daily series, to CSV, JSON or Markdown

Options every report takes

fetch, calculate, contributions and export share these:

-p KEY, --project KEY

The project; without it, the default one (see config default).

--from DAY, --to DAY, --period NAME

The period: the start day is included, the end day excluded.

-u WHO, --user WHO

One person’s share: me, an account id, or part of a name or email (whose work counts).

--as UNIT

Show time amounts in another time unit (units).