jtt login#
Check an Atlassian API token with Jira, then store it securely.

$ jtt login
jtt asks for the Jira site, your account email and an API token. Create the token at
https://id.atlassian.com/manage-profile/security/api-tokens; it is typed hidden. The site can
be written with or without https://: your-team.atlassian.net is enough.
Before storing anything, jtt checks the token with Jira. On success it records your account,
your Jira profile’s time zone (reports use its days) and the site’s working calendar, and
stores the token in the system keyring, or in an owner-only file where there is none (see
Configuration). A rejected token is not stored.
Options skip the questions, for a script. The token prompt stays hidden when --token is
left out:
$ jtt logout
$ jtt login --url your-team.atlassian.net --email you@example.com
To change account or rotate the token, jtt logout first: jtt login refuses
to replace a stored token. Project settings survive a logout, so logging in again finds them.
Options#
jtt login [OPTIONS]
Option |
Default |
Description |
|---|---|---|
|
prompted |
Jira Cloud site URL. |
|
prompted |
The email of the Atlassian account. |
|
prompted |
An Atlassian API token. Prompted, hidden, when omitted. |
|
Show the command’s help and exit. |