Work with Jira and Linear
By CodeLantern Team ·
Jira Cloud and Linear connect as project-management providers while code stays in GitHub. Each repository names its tracker and its source control separately.
Plan in the tracker you already use
Jira Cloud and Linear connect to CodeLantern as project-management providers. Skills read the issue they are working on from your tracker and record their progress back on it, so planning stays where your team already does it.
Source control is its own choice
Jira Cloud and Linear hold the issues. The code stays in GitHub, which keeps the branches and pull requests. Each repository names its project-management provider and its source control separately, and skills use that pairing to find the issue in one place and open the pull request in the other.
Connect it
An admin connects Jira Cloud or Linear under Integrations in the portal, then points a repository at it under Repositories. Each developer also connects their own account, so CodeLantern acts with their permissions. The Admin Setup guide walks through both, and Integrations covers each provider’s requirements.
Improvements (2)
- MCPRepositories. Issue and pull-request tools follow each repository’s configured providers instead of assuming GitHub.
- MCPAuthorization. Skills act with each member’s own provider authorization, kept separate from who the work is attributed to.
Fixes (4)
- PortalLinear. Reconnecting a disconnected Linear integration restores the existing connection instead of failing.
- PortalLinear. Disconnecting Linear revokes every member’s Linear access at the same time.
- PortalLinear. A disconnected Linear integration can be removed, the same as GitHub and Jira.
- PortalJira and Linear. Authorization returns to the portal address that started it, so the sign-in session carries through.
Availability
Live for CodeLantern customer organizations. An admin connects Jira Cloud or Linear and configures each repository, and each developer connects their own account. Onboarding is still required.