Issue Tracker Integrations

Last updated: June 2026

Overview

Connecting an issue tracker lets you create a Kepler Task (the core unit of work in Kepler’s Agentic Development Environment, or ADE) directly from an issue. Kepler passes the issue title, description, and metadata to the agent automatically as its starting context.

Supported trackers

Tracker	Auth method	Self-hosted support
Jira	OAuth 2.0	No (Cloud only)
Linear	OAuth 2.0	No
Trello	OAuth 2.0	No
GitHub Issues	OAuth 2.0	No
GitHub Enterprise Issues	Personal Access Token	Yes
GitLab Issues	OAuth 2.0	No
GitLab Self-Hosted Issues	Personal Access Token	Yes
Azure DevOps	OAuth 2.0	No

---

Jira

Prerequisites

• A Jira Cloud account with permission to install OAuth apps.
• A Kepler account with at least one workspace configured.

Connect Jira

1. Open Kepler and navigate to Settings → Integrations.
2. Under Issue Trackers, click Connect next to Jira.
3. Click Authorize with Jira. You will be redirected to Atlassian’s OAuth flow.
4. Select the Jira site you want to connect and click Accept.
5. Kepler shows Jira connected with your site name.

What Kepler pulls from Jira

When you create a Task from a Jira issue, Kepler passes the following fields to the agent:

• Issue key and summary (title)
• Description (including formatted text and code blocks)
• Labels
• Assignee
• Priority
• Status
• Linked issue keys

Limitations

• Jira Data Center and Jira Server are not supported. Use the GitHub Enterprise or GitLab Self-Hosted integration for self-managed workflows.
• Attachments and embedded images in issue descriptions are not passed to the agent.

---

Linear

Prerequisites

• A Linear workspace with member or admin access.

Connect Linear

1. In Kepler, go to Settings → Integrations.
2. Under Issue Trackers, click Connect next to Linear.
3. Click Authorize with Linear. Linear’s OAuth consent screen opens.
4. Select the workspace to connect and click Allow access.
5. Kepler shows Linear connected when the authorization completes.

What Kepler pulls from Linear

Creating a Task from a Linear issue passes these fields to the agent:

• Issue identifier and title
• Description (Markdown)
• Labels
• Assignee
• Priority
• State (status)
• Project and cycle membership

Limitations

• Sub-issues are not recursively fetched; only the selected issue’s fields are passed.

---

Trello

Prerequisites

• A Trello account with access to the boards you want to use.

Connect Trello

1. In Kepler, open Settings → Integrations.
2. Under Issue Trackers, click Connect next to Trello.
3. Click Authorize with Trello. Trello’s OAuth consent screen opens.
4. Click Allow.
5. Kepler confirms the connection with Trello connected.

What Kepler pulls from Trello

From a Trello card, Kepler passes:

• Card name (title)
• Card description
• Labels
• Members (assignees)
• Due date
• Checklist names and items

Limitations

• Card attachments are not passed to the agent.
• Custom fields are not currently supported.

---

GitHub Issues

Prerequisites

• A GitHub account with access to the repositories whose issues you want to use.

Connect GitHub Issues

1. In Kepler, navigate to Settings → Integrations.
2. Under Issue Trackers, click Connect next to GitHub Issues.
3. Click Authorize with GitHub. GitHub’s OAuth app authorization page opens.
4. Select the organizations and repositories to grant access to, then click Authorize.
5. After authorization, Kepler shows GitHub connected.

What Kepler pulls from GitHub Issues

Kepler reads these fields from the GitHub issue:

• Issue number and title
• Body (Markdown)
• Labels
• Assignees
• Milestone
• Linked pull request references

Limitations

• GitHub Projects (v2) fields beyond the standard issue fields are not passed.
• Private repositories require the repo OAuth scope; Kepler requests this during authorization.

---

GitHub Enterprise Issues

Prerequisites

• A GitHub Enterprise Server instance (3.x or later recommended).
• A personal access token (PAT) with repo scope, generated on your GitHub Enterprise instance.
• Your GitHub Enterprise Server hostname (e.g., github.yourcompany.com).

Connect GitHub Enterprise Issues

1. Go to Settings → Integrations in Kepler.
2. Under Issue Trackers, click Connect next to GitHub Enterprise Issues.
3. Enter your Server URL (e.g., https://github.yourcompany.com).
4. Paste your Personal Access Token.
5. Click Connect. Kepler verifies the token and shows GitHub Enterprise connected.

What Kepler pulls from GitHub Enterprise Issues

Kepler pulls the same fields as GitHub Issues (see above). Field availability depends on your GitHub Enterprise Server version.

Limitations

• GitHub Enterprise Cloud (GHEC) with an enterprise account uses the standard GitHub Issues integration above, not this one.
• Tokens are stored per user; each team member must connect their own PAT.

---

GitLab Issues

Prerequisites

• A GitLab.com account with access to the projects whose issues you want to use.

Connect GitLab Issues

1. In Kepler, open Settings → Integrations.
2. Under Issue Trackers, click Connect next to GitLab Issues.
3. Click Authorize with GitLab. GitLab’s OAuth consent screen opens.
4. Click Authorize.
5. The page returns to Kepler showing GitLab connected.

What Kepler pulls from GitLab Issues

From a GitLab issue, Kepler passes:

• Issue IID and title
• Description (Markdown)
• Labels
• Assignees
• Milestone
• Weight (if set)
• Linked issue references

Limitations

• GitLab EE-only fields (e.g., epic membership, health status) are not currently passed.

---

GitLab Self-Hosted Issues

Prerequisites

• A self-managed GitLab instance (GitLab CE or EE, 15.x or later recommended).
• A personal access token with api scope, generated on your GitLab instance.
• Your GitLab instance URL (e.g., https://gitlab.yourcompany.com).

Connect GitLab Self-Hosted Issues

1. Go to Settings → Integrations in Kepler.
2. Under Issue Trackers, click Connect next to GitLab Self-Hosted Issues.
3. Enter your Instance URL (e.g., https://gitlab.yourcompany.com).
4. Paste your Personal Access Token.
5. Click Connect. Kepler verifies the token and shows GitLab Self-Hosted connected.

What Kepler pulls from GitLab Self-Hosted Issues

Kepler pulls the same fields as GitLab Issues (see above). Field availability depends on your GitLab version and edition.

Limitations

• The GitLab instance must be reachable from your machine. Air-gapped instances are not supported unless Kepler is deployed in your network.
• Tokens are stored per user; each team member must connect their own PAT.

---

Azure DevOps

Prerequisites

• An Azure DevOps organization with member or higher access.
• Work items enabled on the project(s) you want to use.

Connect Azure DevOps

1. In Kepler, navigate to Settings → Integrations.
2. Under Issue Trackers, click Connect next to Azure DevOps.
3. Click Authorize with Azure DevOps. Microsoft’s OAuth consent screen opens.
4. Sign in with your Microsoft account and click Accept.
5. Kepler shows Azure DevOps connected with your organization name.

What Kepler pulls from Azure DevOps

From an Azure DevOps work item, Kepler passes:

• Work item ID and title
• Description
• Work item type (Bug, User Story, Task, etc.)
• Tags
• Assigned to
• State
• Area path and iteration path

Limitations

• Azure DevOps Server (on-premises) is not currently supported.
• Rich text formatting in work item descriptions may be partially stripped when passed to the agent.

---