Connect work sources

Part of Gateway → Developers.

Workspace admins and members with sessions:admin can connect Jira, ClickUp, Linear, and GitHub. Developer reporting requires the Enterprise plan. Work sources must be enabled for your workspace.

Connect a tracker

The credential needs read access to the work you want to import. Connect a tracker before GitHub if you want to associate pull requests with tasks.

1. Open work sources

   Open Gateway → Developers → Setup → Configuration → Work sources. Choose Connect or manage, then select a tracker.

2. Enter credentials

   Enter the credential and an optional connection name. For Jira, enter the site URL and account email too. Choose Choose projects, Choose lists, or Choose teams.

3. Choose the work to import

   Select the projects, lists, or teams. For ClickUp, choose a workspace first. Choose Load more if the list has more results. Only selected work is imported and available for association.

4. Save and check the import

   Choose Save connection to queue the import. Use Check import status to check its progress.

Connect GitHub

Create a fine-grained GitHub token for the repositories you want to import. Grant read access to Pull requests, Contents, Checks, Actions, and Deployments as needed. Missing optional permissions appear as connection limitations.

1. Open GitHub setup

   Under Work sources, choose Connect or manage, then GitHub.

2. Enter repositories and token

   Enter a connection name, the token, and repositories as owner/name, one per line. Each connection accepts repositories from one GitHub owner.

3. Choose trackers

   Select at least one connected Jira, ClickUp, or Linear tracker. Only explicit task references within the selected trackers are eligible for association.

4. Connect and check the import

   Choose Connect GitHub to save the connection and queue the import. Use Check import status to check its progress.

Refresh or reconnect a source

In Connect or manage, inspect the status, last import, and any Import limitations. Choose Refresh source to queue another import. If a source needs attention, reconnect it and check the credential's access. Previously imported work remains available when a refresh fails.

A saved connection or queued refresh does not mean the import has completed. Check the status and imported data before using the results.

Review task associations

Automatic linking requires a compatible preview CLI and an enabled deployment. See Release channels before installing it. Select session sync in setup and approve reporting the available repository and branch context. No task picker is required before each session.

A session can link when its branch names one task in a selected tracker scope, or when its repository and branch match a pull request with an explicit task reference. Connect the tracker and the GitHub repository for the pull-request path. Ambiguous or out-of-scope references stay unlinked.

Once captured sessions have linked, open Personal → Usage & costs → By task or Team → Economics → By task, subject to your workspace permissions. Connections opens the same source-management drawer from either view. Tasks appear after at least one confirmed session link. Unmatched sessions stay in ordinary session activity; the task table is not your tracker's full backlog.

Open a task title to inspect its sessions. Select a suggestion count to review pending associations. You can remove eligible links for sessions you own, or accept or reject suggestions. Required task context set by your coding client must be changed there. Explicit removals are preserved when evidence refreshes.

Read task usage

• Session tokens include confirmed and suggested sessions associated with the task. A session shared with another task can appear in both rows.
• Task cost estimate includes priced, confirmed sessions exclusive to that task. Suggested and shared sessions are excluded. Partial is the known attributable portion, not the full task cost.
• Unknown usage stays unknown. An unavailable estimate is not zero.
• Totals count shared and parent-inclusive usage once. Do not add task rows together; their sessions can overlap.

Select the usage help or warning icon beside search for How usage is counted and any capture limitations. Estimates are separate from provider invoices and subscription fees.

Next