Feature request
Add an integration with Azure DevOps Boards so that users can connect an Azure DevOps project/board and select existing work items as SlayZone tasks.
Problem
In the current workflow, I give an AI coding agent an Azure DevOps task ID and have the agent retrieve the task details from Azure DevOps. This works, but it is not a smooth experience. I have to manually create a corresponding task in SlayZone even when the task already exists in Azure DevOps or has already been completed there, which can result in duplicate task entry and unnecessary context switching.
Proposed solution
- Allow users to connect an Azure DevOps organization/project, using the appropriate Azure DevOps authentication flow.
- Provide a way to browse or search Azure DevOps Boards work items from within SlayZone.
- Allow an existing Azure DevOps work item to be selected as, or linked to, a SlayZone task.
- Import the relevant work-item information—such as title, description, status, acceptance criteria, and task ID—into the SlayZone task context.
- Preserve a link back to the Azure DevOps work item.
- Ideally, keep task status synchronized or provide an explicit refresh/update action so users do not need to duplicate completed work manually.
Expected benefit
This would make it possible to start work in SlayZone directly from an existing Azure DevOps task, giving AI coding agents the correct context without requiring users to manually recreate tasks or repeatedly provide task IDs.
Additional context
The primary use case is selecting an Azure DevOps task from the SlayZone interface and then using that task as the context for an AI coding session.
Feature request
Add an integration with Azure DevOps Boards so that users can connect an Azure DevOps project/board and select existing work items as SlayZone tasks.
Problem
In the current workflow, I give an AI coding agent an Azure DevOps task ID and have the agent retrieve the task details from Azure DevOps. This works, but it is not a smooth experience. I have to manually create a corresponding task in SlayZone even when the task already exists in Azure DevOps or has already been completed there, which can result in duplicate task entry and unnecessary context switching.
Proposed solution
Expected benefit
This would make it possible to start work in SlayZone directly from an existing Azure DevOps task, giving AI coding agents the correct context without requiring users to manually recreate tasks or repeatedly provide task IDs.
Additional context
The primary use case is selecting an Azure DevOps task from the SlayZone interface and then using that task as the context for an AI coding session.