Jira
roots supports both Jira Cloud and Jira Server / Data Center. It imports worklogs — the time you've logged on Jira issues.
Multiple Connections
You can connect multiple Jira instances at the same time — for example a Cloud instance and a Server instance during a migration. Worklogs from all connections appear together in the Jira column.
Jira Cloud
What You Need
| Setting | Value |
|---|---|
| Base URL | your-domain.atlassian.net |
| Your Atlassian account email | |
| API Token | Token from Atlassian account settings |
Creating an API Token
- Go to Atlassian API Tokens
- Click Create API token
- Enter a label (e.g. "roots")
- Copy the generated token
WARNING
The token is shown only once. Store it securely before closing the dialog.
Connect in roots
- Open the Connection Manager
- In the Jira section, click + Add Connection (or fill the form if no connection exists yet)
- Optionally enter a label (e.g. "Cloud Production") — auto-derived from the URL if left empty
- Choose Cloud as instance type
- Enter your Atlassian URL (e.g.
company.atlassian.net) - Enter your email and paste the API token
- Click Connect
Jira Server / Data Center
What You Need
| Setting | Value |
|---|---|
| Base URL | https://jira.your-company.com |
| Auth method | Personal Access Token (PAT) or Username + Password |
Option A: Personal Access Token (recommended)
- Log in to your Jira Server instance
- Go to Profile → Personal Access Tokens
- Click Create token
- Set a name and optional expiration date
- Copy the token
Option B: Basic Authentication
Use your Jira username and password. This method is less secure and may not work if your organization enforces SSO.
TIP
PAT authentication is recommended over username/password for better security and compatibility.
Connect in roots
- Open the Connection Manager
- In the Jira section, click + Add Connection
- Optionally enter a label (e.g. "On-Premise DC")
- Choose Server / Data Center as instance type
- Enter the full base URL of your Jira instance
- Select auth method (PAT or Basic) and enter credentials
- Click Connect
Multiple Connections
You can add as many Jira connections as you need. Each connection is listed in the Connection Manager with its label and status.
- Click + Add Connection to add another instance
- Click Remove to disconnect a single instance
- Click Retry if a connection failed
When multiple connections are active, each worklog card in the timeline shows a small label indicating which instance it belongs to.
What roots Fetches
| Data | Description |
|---|---|
| Worklogs | Time logged by you on any issue within the selected date range |
| Issue metadata | Issue key, summary, type and project (for display context) |
roots uses JQL to find issues with worklogs in the selected date range, then filters for your entries.
Features
- View worklogs with issue key, summary and time spent
- Create, edit and delete worklogs directly from roots
- Issue link — click an issue key to open it in Jira
Troubleshooting
"Authentication failed"
- Cloud: Verify email matches your Atlassian account. Regenerate the API token if expired.
- Server: Check that PATs are enabled by your admin. For basic auth, verify your username (not email).
"No worklogs found"
- roots only shows worklogs authored by you. Entries from other users are filtered out.
- Check that you have worklogs for the selected date — roots searches by
worklogDate, not issue creation date.
Rate limiting (429)
- Jira Cloud has API rate limits. roots retries automatically with exponential backoff.
- If persistent, reduce the date range or wait a few minutes.