Plan and ship in Azure DevOps
By CodeLantern Team ·
CodeLantern connects to Azure Boards for project management and Azure Repos for source control, both part of Azure DevOps Services.
Plan and ship in Azure DevOps
CodeLantern works with Azure DevOps Services in both roles. Azure Boards is a project-management provider: skills read, create, update, tag, and comment on work items, and map Priority and Size to your project’s own fields.
Azure Repos handles source control: skills open and update pull requests, post inline and general review comments, and link each pull request to its work item.
Pair it with what you already use
Boards and Repos can sit in different projects of the same organization. Azure Boards also pairs with GitHub for code, and Azure Repos pairs with Jira Cloud or Linear for planning. GitHub issues need GitHub source control, so that is the one combination Azure Repos doesn’t support.
Connect it
An admin connects an Azure DevOps Services organization under Integrations with a Microsoft account. One connection covers the projects in that organization. For changes made in Azure Boards to flow back to CodeLantern automatically, the admin needs Project Administrator on that project; without it the portal shows a warning and repository work carries on.
Each developer then connects their own Azure DevOps account. The Integrations and Repositories guides cover permissions and project selection.
Improvements (2)
- Plugincl-init. Recognizes dev.azure.com, *.visualstudio.com, and Azure SSH remotes, including the project, so an Azure repository reads as configured.
- PluginWork items. When project management and source control are different providers, pull requests reference the work item by its key instead of a # link that would point at the wrong tracker.
Fixes (2)
- MCPPull requests. Azure pull requests return a working browser link instead of an empty one.
- PluginReferences. Agent-written pull request and issue text follows each provider’s reference syntax, so an Azure pull request is no longer written as #n, which Azure reads as a work item.
Availability
Live for CodeLantern customer organizations. An admin connects the Azure DevOps Services organization and configures each repository, and each developer connects their own account. Onboarding is still required.