Frontmatter:
title: Issue Tracker Integrations
description: Connect your issue tracker to Kepler so you can create Tasks directly from issues and pass issue context to your agents automatically.
taxonomy:
category: kepler
Purpose: Setup reference for all supported issue trackers. Covers authentication, what context passes to the agent, and any per-tracker notes.
Sections to include:
Overview
Why connect an issue tracker: create a Task from an issue and have Kepler pass the issue title, description, and metadata to the agent automatically as its starting context.
Summary table: Tracker | Auth method | Self-hosted support.
Supported trackers: Jira, Linear, Trello, GitHub Issues, GitHub Enterprise Issues, GitLab Issues, GitLab Self-Hosted Issues, Azure DevOps.
Per-tracker setup (one sub-section each):
Jira | Linear | Trello | GitHub Issues | GitHub Enterprise | GitLab | GitLab Self-Hosted | Azure DevOps
Each sub-section covers:
Prerequisites.
Step-by-step connection instructions.
What Kepler pulls from the tracker (issue title, description, labels, assignee, etc.).
Any limitations or self-hosted requirements.
Frontmatter:
title: Issue Tracker Integrations
description: Connect your issue tracker to Kepler so you can create Tasks directly from issues and pass issue context to your agents automatically.
taxonomy:
category: kepler
Purpose: Setup reference for all supported issue trackers. Covers authentication, what context passes to the agent, and any per-tracker notes.
Sections to include:
Overview
Why connect an issue tracker: create a Task from an issue and have Kepler pass the issue title, description, and metadata to the agent automatically as its starting context.
Summary table: Tracker | Auth method | Self-hosted support.
Supported trackers: Jira, Linear, Trello, GitHub Issues, GitHub Enterprise Issues, GitLab Issues, GitLab Self-Hosted Issues, Azure DevOps.
Per-tracker setup (one sub-section each):
Jira | Linear | Trello | GitHub Issues | GitHub Enterprise | GitLab | GitLab Self-Hosted | Azure DevOps
Each sub-section covers:
Prerequisites.
Step-by-step connection instructions.
What Kepler pulls from the tracker (issue title, description, labels, assignee, etc.).
Any limitations or self-hosted requirements.