Last updated: November 2026
Connect an issue tracker to see the issues you are working on in the Kepler interface, alongside your pull requests and the tasks you already have running. To start work on an issue, you pick its row instead of describing the work from scratch.
You manage providers in the Issues and pull requests section of Settings → Integrations.

Trackers Kepler can read issues from
Of Kepler’s 13 providers, 11 return issues:
| Provider | Also returns pull requests |
|---|---|
| GitHub | Yes |
| GitHub Enterprise | Yes |
| GitLab | Yes |
| GitLab Self-Hosted | Yes |
| Azure DevOps | Yes |
| Azure DevOps Server | Yes |
| Jira | No |
| Jira Server / Data Center | No |
| Linear | No |
| Trello | No |
| Asana | No |
Jira, Linear, Trello, and Asana do not appear in pull-request filters.
The other 2 providers, Bitbucket and Bitbucket Data Center, return pull requests only. See Pull Request Integrations.
Kepler supports self-hosted instances. GitHub Enterprise, GitLab Self-Hosted, Azure DevOps Server, and Jira Server / Data Center read issues the same way their cloud counterparts do. Which fields come back depends on your server’s version, and your machine needs to be able to reach the server. You connect a self-hosted instance inside Kepler with its address and a personal access token. See Connect a self-hosted tracker.
Kepler trusts the certificates installed in your operating system’s certificate store, so a server signed by your company’s own certificate authority, or a network that re-signs HTTPS traffic, works without extra setup.
Connect a tracker
To connect a cloud tracker (GitHub, GitLab, Azure DevOps, Jira, Linear, Trello, or Asana), follow these steps:
- Open Settings → Integrations.
- Find the provider in Issues and pull requests and click Connect.
- Authorize Kepler on GitKraken’s website, which opens in your browser.
- Return to Kepler, where the provider shows a Connected badge.
Integrations belong to your GitKraken account, not to this copy of Kepler, so a provider you connect here is also available to the gk command-line interface (CLI) and GitKraken Desktop. To manage integrations, sign in to a GitKraken account. Kepler prompts you if you are not signed in.
If your browser did not open, copy the Connection link from the dialog Kepler shows while you authorize, and open it in a browser yourself. Each link works once, so Try again makes a new one. The dialog closes by itself once the connection appears.
Connect a self-hosted tracker
GitHub Enterprise, GitLab Self-Hosted, Azure DevOps Server, and Jira Server / Data Center connect inside Kepler with a personal access token rather than through the browser:
- Open Settings → Integrations.
- Find the provider in Issues and pull requests and click Connect. The Connect provider dialog opens.
- In Server URL, enter the server’s address, including the port and installation path when your server uses them.
- In Personal access token, paste a token with access to the issues you need.
- Click Save connection.

Kepler checks the token against the server from your machine, saves it on this device, and adds the connection to your GitKraken account. The dialog reports one of these results:
- The server accepted the token.
- Kepler saved the token without being able to reach the server or verify its certificate.
- The server refused the token: The server refused this token. Check its value and permissions.
For every message the dialog shows, see Pull Request Integrations. Until Kepler finishes syncing the connection to your account, the provider’s row shows Cloud sync pending.
Once connected, a self-hosted provider lists each server on its own row, with Set as primary, Replace token, and Disconnect. Each server keeps its own repositories and issues:
- To connect another server, click Add connection on the provider’s row.
- To renew an expired or rejected token, click Replace token on that server’s row.
- To make a server the provider’s default connection, click Set as primary. Agents’ GitKraken MCP server acts through the primary connection.

Use these controls to manage connected providers:
| Control | What it does |
|---|---|
| Reconnect | Runs authorization again. Use it when a sign-in has expired |
| Disconnect | Removes the provider’s primary connection. See Disconnect a provider |
| Refresh | At the top of the section, checks every provider again |
A provider’s row can also show a warning:
| Warning | What it means | What to do |
|---|---|---|
| Sign-in expired | The provider’s sign-in has expired | Wait for Kepler to refresh it, or click Reconnect |
| Cannot connect to server | Kepler could not reach the server; the integration is still connected | Check that the server is reachable from your network or VPN; the warning clears on its own |
| Unexpected response | Kepler could not read the provider’s answer, so some items may be missing | Reconnecting does not help; if it stays, check for a proxy or gateway between Kepler and the provider |
| An organization named under the row | That organization refuses Kepler’s access, so only its items are left out | Follow the row’s advice, such as Request access on GitHub |
You do not have to open Settings to find a failing provider. Todo, the Resources screen’s lists, and a link preview name it too, with the one fix that applies: Reconnect, Reconnect in settings for a self-hosted provider, Open settings, or Retry. See Pull Request Integrations for each warning.
Choose what Kepler brings in
Each connected integration except Trello and Asana has a visibility line under its row in Settings → Integrations. The line reads Everything visible, or how many items you have hidden.
To hide part of an integration:
- Click Choose what’s visible… on the provider’s row. The Choose what provider brings in dialog opens.
- Clear the checkbox of each item to hide. Type in Filter… to narrow a long list.
- Click Save.

What the dialog lists depends on the provider:
| Provider | Lists |
|---|---|
| GitHub, GitHub Enterprise, GitLab, GitLab Self-Hosted, Bitbucket, Bitbucket Data Center | Organizations and Repositories |
| Azure DevOps, Azure DevOps Server | Organizations, Repositories, and Projects |
| Jira, Jira Server / Data Center, Linear | Projects |
A ticked item is visible. Hiding an organization also hides its repositories, which show Hidden with its organization and cannot be ticked on their own. A hidden project leaves the issue lists but stays in the project pickers. A project that has not returned any issues yet may be missing from the dialog’s list.
Hidden items are left out of Todo, the issue and pull request lists, and the pickers. Tasks and branches already linked to a hidden item keep working. Kepler saves the choice on your GitKraken account, so it follows you to other machines where you sign in.
More than one account of the same provider
You can connect several accounts of the same provider: two GitHub accounts, a work Jira site and a personal one. When a provider has two or more, an Accounts list appears under its row with one entry per account.
Each entry carries two independent controls:
| Control | What it changes | How far it reaches |
|---|---|---|
| Read from this account | Which account Kepler reads this provider’s issues and pull requests from | Kepler only, and non-destructive |
| Set as primary / Primary | The provider’s primary account | Everywhere: other Kepler windows, the gk CLI, and GitKraken Desktop |
Browsing a secondary account does not change your primary. Selecting Read from this account on a second account switches what Kepler shows you and leaves the primary as it is. The primary is the default read account, so a provider with no override reads through it.
Agents keep acting as the primary account. Your agents’ GitKraken MCP server always uses the primary connection of your GitKraken account, even when Kepler reads a provider through another account.
Changing either one clears that provider’s saved filters.
Reconnect keeps your choices. When one account’s sign-in fails, Reconnect renews that account’s connection and keeps your primary and read choices.
The read account also authenticates Git. When you start work on an issue in a repository you have never cloned, Kepler clones that repository with the same connection it reads through. See Pull Request Integrations for which hosts this covers and what happens on the hosts it does not.
Linear connections stay separate by workspace. Each Linear account’s entry shows the Linear workspace it was granted. Connections to different workspaces are separate accounts, each reading only its own workspace’s issues.
Disconnect a provider
Click Disconnect on the provider’s row in Settings → Integrations and confirm.
Disconnecting affects more than Kepler: it removes the connection from your GitKraken account, so the gk CLI and GitKraken Desktop lose it too. What happens to the provider depends on whether you have another account connected:
- With another account connected, Kepler promotes it to primary and the provider stays connected under it. Nothing else changes.
- With no other account connected, Kepler removes the provider entirely, with its saved filters and its rows in your lists.
You can reconnect at any time.
What Kepler reads from an issue
When an issue becomes a task, Kepler attaches what it read, so the agent starts with that context instead of asking for it. Kepler reads these fields from the issue:
| Field | Notes |
|---|---|
| Identifier | The issue key or number: GK-1234 for Jira, DRE-2 for Linear, a number for GitHub, GitLab, and Azure DevOps |
| Title | |
| Description | The issue body, or an Azure DevOps field such as Repro Steps on a Bug, labeled with its name |
| Issue type | The provider’s own type, such as a Jira issue type |
| Author | When the provider reports one |
| Assignees | |
| Status | The issue’s current state, in the provider’s own words, such as Jira’s To Verify |
| Last updated | When the issue was last updated |
| Labels | The provider’s own labels, shown as badges in issue previews |
| Project or board | Jira projects, Linear teams, Azure DevOps areas. Git hosts attach issues to a repository instead |
| Iteration or sprint | Azure DevOps iterations and Jira sprints. A Jira issue carried across sprints keeps them all |
| Repository | Name, owner, and host, for the git hosts |
| URL | Used by the open control, which names the provider: Open on GitHub, Open on Jira, and so on |
Kepler does not read an issue’s priority field, due date, Trello checklist, or Linear cycle. An agent can still find these by opening the issue’s URL itself, but Kepler does not deliver them as attached context.
Kepler reads an issue’s milestone on GitHub, GitHub Enterprise, GitLab, GitLab Self-Hosted, and Linear, so Todo can group and filter by Milestone. See Arranging Your Work.
Todo’s Priority grouping and filter come from labels instead: a label such as P1, priority: high, blocker, or critical sets the level, and the most urgent label wins. Jira and Linear keep priority in a field Kepler does not read, so their issues show as Unprioritised unless a label sets a priority. See Arranging Your Work.
Jira and Azure DevOps descriptions keep their headings, code blocks, and tables in Kepler’s previews and in the agent’s context.
Images embedded in an issue’s description, including Jira and Azure DevOps attachments, display in Kepler’s issue previews, from self-hosted servers too. The agent receives the description as text: Kepler does not pass the attachments or images themselves.
Comments
When you open an issue in a reader, either the task panel’s side pane or the issue’s pane on the task page, a Comments section under the summary shows its discussion. Kepler reads comments for GitHub, GitHub Enterprise, GitLab, GitLab Self-Hosted, Jira, and Jira Server / Data Center. For other providers, the section says that comments for that provider are not available in Kepler yet.
Kepler shows up to the newest 100 comments, newest at the bottom. Show earlier comments shows older ones, and Refresh comments reads the discussion again. Comments are for you to read: Kepler does not attach them to the task or pass them to the agent.
Which issues Kepler lists
Kepler lists open work. An issue that is finished or canceled in its tracker (a Linear issue in Done or Canceled, for example) leaves Todo and the issue pickers. An issue already attached to a task keeps showing on that task with its real state, finished or not.
A Todo view has 2 scopes, set in its View menu under Scope:
- Mine: the issues related to you, across every organization you belong to.
- All: also adds the open issues of the repositories added to Kepler on GitHub, GitHub Enterprise, GitLab, and GitLab Self-Hosted. On other providers, it lists the same issues as Mine.
Under All, Repos and Updated narrow the view by repository and by how recently each issue was updated. All repos in Kepler skips a very large repository and says so, with Choose repos to add it anyway.
Under Mine, each provider reports a different set of issues related to you:
| Provider | Issues Todo lists |
|---|---|
| GitHub, GitHub Enterprise | Yours, assigned to you, or mentioning you |
| GitLab, GitLab Self-Hosted, Azure DevOps, Azure DevOps Server | Yours or assigned to you |
| Jira, Jira Server / Data Center, Linear, Trello, Asana | Assigned to you |
An issue listed only because you were mentioned is marked Mentioned, so you can tell it apart from work that is yours. Under All, the Your role filter also offers Not mine.

To find issues to add to a task, the issue list on a task’s Resources screen has its own scope menu: Related to me, All in my repos (the open issues in the repositories added to Kepler), or All visible.
For GitHub and Azure DevOps, All visible reads every issue across your organizations, including repositories you can read outside them, such as ones where you are an outside collaborator. It loads more slowly. Jira and Linear show only your issues there until you pick a project or a team:
- Jira: when the issue list shows Jira alone, a project picker appears, starting with All projects. Pick a project to see every open issue in it. Kepler remembers the pick for each Jira connection.
- Linear: when the issue list shows Linear alone, a team picker and a Project picker appear. Pick a team, a Linear project, or both, to see every open issue in them, whoever it is assigned to. The Project picker lists your Linear workspace’s projects with their state, closed ones included.
A Linear issue synced with GitHub shows once. When Linear’s GitHub Issues sync keeps a two-way copy of a Linear issue on GitHub, Kepler lists the pair as one row, the Linear issue. The pair shares one task history, so a task started from either copy is the issue’s task. Pairing works for GitHub.com and GitHub Enterprise Cloud.
When you start work from the Linear issue, Kepler uses the repository of its GitHub copy if exactly one repository you have in Kepler matches it.
Where your issues turn up
Your issues appear in 3 places:
| Surface | What it gives you |
|---|---|
| The Kepler interface | A Todo view lists your issues across every connected tracker, grouped and filtered how you like |
| Actions | The Action button on a row hands the issue to an agent with its context attached. Running an Action on an issue that has no task also turns it into a task |
| Tasks and Resources | An issue is a resource on a task, so you can attach one to work that already exists |
The Issue type, Label, Project, and Status filters use your provider’s own terms, not Kepler’s. Azure DevOps and Jira issues also filter by Iteration and Sprint, each named the way its tracker names it.
Kepler recognizes an issue from its URL when you paste or attach one, including these work item URLs:
- GitLab work items, at
/-/work_items/<number>in a project. A group-level work item stays a plain link. - Azure DevOps work items, at
/<organization>/<project>/_workitems/edit/<number>or at the organization level,/<organization>/_workitems/edit/<number>.
Search by key or link. In the issue list of a task’s Resources screen, type a Jira or Linear issue key, such as OPS-42, or paste a Jira Cloud, Jira Server / Data Center, Linear, or Azure DevOps work item link. Kepler finds that issue in its tracker, whatever its state, even when it is not in the list. A Jira Server / Data Center link resolves when it points at an installation you have connected.
Jira keys in commits and branches. With Jira or Jira Server / Data Center connected, Kepler links Jira issue keys in commit messages and branch names, so OPS-42 in a commit message links to that issue. Right-click a commit in a worktree’s commit list for Open issue key and Copy issue URL for key (see Review What a Coding Agent Changed), and the Worktrees and branches page shows the keys as chips on branch and worktree rows (see Repository Settings). Only Jira keys are linked this way.
Add from the list with the keyboard. In the issue list on the Resources screen, the arrows move between rows, and Enter or a double-click adds the row. Show preview in the screen’s header shows the picked row beside the list. See Picking issues and pull requests.
Paste a link on the Links tab. An issue URL pasted on the Links tab of the Resources screen is looked up and added as that issue, with Add as plain link to keep it a plain link. See Pasting an issue link.
Paste a link into a prompt. Paste an issue or pull request URL into a session’s or a new task’s composer and it becomes a link chip, which Kepler attaches to the task when you send. See Sending a prompt.