Connect Jira, GitHub, Linear or Asana
Ask AI
Connect Jira, GitHub, Linear or Asana, log hours against a real issue, and see which fields the tracker owns
A tracker connection lets people attach a Jira, GitHub, Linear or Asana issue to a time entry. Nothing syncs: an issue becomes a work item the first time someone logs hours against it.
Connect a tracker (admin)
Settings → Issue trackers (admin only) lists one row per tracker. Verify & connect calls the tracker before anything is written: a rejected credential fails the connect and nothing is stored, and a token that passes is stored encrypted.
| Tracker | Credentials | Search | Issue scope |
|---|---|---|---|
| Jira | Site URL, the token's email, an API token from id.atlassian.com | Keys resolve directly in one lookup; other terms search summaries without an age cutoff | Project key in capitals, PLAT |
| GitHub | Organization login, fine-grained token that can read its issues | Full text over the scoped repositories' issues, pull requests filtered; keys read owner/repo#123 | owner/repo |
| Linear | API key, bound to its own workspace | Full-text search within the scoped teams | Team key in capitals, ENG |
| Asana | Personal access token; pick a workspace when the token sees several | Titles of the first 100 open tasks in up to 3 scoped projects | Project gid, from its URL |
Scope a project to a tracker
The project form under Time tracking → Projects carries Issue source (the provider) and
Issue scope (the container from the table above - Northlake pins Platform v2 to
northlake/platform). Only an admin sets them, and a scope without the tracker's shape, such as a
lowercase Jira key, is refused on save. A tracker is only searched inside the scopes of the
projects involved: a project with no scope gets no tracker results.
Log time against an issue
Open Add work item from My time (week or day view). Search starts at 3 characters and covers the picked project's scope, or with no project picked, the scopes of all your projects (the ones you are on or logged to in the last 30 days). Source limits it to one tracker.
A saved issue can be selected directly. A new issue goes to the project whose scope it came from; when several of your projects share that scope, the picker asks which. The first log creates one work item keyed on project, provider and issue id; later logs reuse it. Searching and selecting alone create nothing.
Jira accepts exact keys such as PLAT-999 when PLAT is in scope. Saved tracker work stays
searchable when its connection fails, and an unavailable tracker is named beside the other results,
never shown as an empty search. Searches are rate-limited per workspace and tracker, never retried
automatically, and capped at 20 results; with Source set to Activities, Load more
fetches the next page.
Link your account
Link your tracker identity under Preferences → Connected accounts. Picking a project in Add work item then lists Your open issues: the open issues assigned to you within its scope, up to a minute old. Search marks them Assigned to you. Without a linked account the picker shows a Link your Jira account line (naming the project's tracker) instead.
What the tracker owns
A work item stores the issue reference and title on its first log, and keeps the issue's link only when it is an https link on the tracker's own site. No worklog is written back to the tracker. Assignment is live discovery information, not a synchronized local catalog. An issue-backed work item cannot be renamed and is not listed on a project's Activities tab; an admin can still set its time category through an agent. Disconnecting leaves recorded hours and saved issue references intact.