Harness- ADO Boards Integration
under review
D
Domestic Pigeon
We are requesting a native integration between Harness and Azure DevOps (ADO) Boards to automatically create work items for pipeline failures.
Currently, we attempted to use Harness → ServiceNow integration for incident management, but we faced a major limitation in our operating model:
Applications are supported by multiple PODs (teams)
ServiceNow requires a single assignment group at ticket creation
Harness does not have sufficient context to dynamically determine the correct assignment group
This results in:
Incorrect incident routing
Manual reassignment efforts
Increased MTTR and reduced operational efficiency
To address this, we are moving toward using ADO Boards for failure tracking, where:
Work items can be mapped to area paths / teams
Ownership can be aligned more accurately with POD-based support models
Log In
D
Domestic Pigeon
Hi Shylaja,
Thanks for reviewing the feature request. Please find the additional details below:
What kind of failures need ticket creation?
We are primarily looking for automatic work item/ticket creation for deployment or pipeline failures that require operational follow-up or manual intervention. Examples include:
Deployment failures
Infrastructure provisioning failures
Application health check failures
Verification/approval stage failures
Rollback failures
Timeout or execution failures during release
Should these tickets be created during release time?
Yes. The expectation is to create work items in real time during release/deployment execution so that the responsible POD/team
Are multiple services released together, and should failures from other tasks also create tickets?
Yes, multiple applications/services may be released as part of a release window or deployment pipeline. If any critical task/service deployment fails, the integration should be able to create corresponding ADO Board work items based on configured failure conditions and ownership mapping.
With ADO Boards:
Work items can be mapped to Area Paths/Teams
Ownership alignment is more flexible
POD-based operational support can be managed more effectively
Also, could you please schedule a discussion call with the relevant teams so we can review the requirements and expected workflow in more detail?
Thanks,
Baji Patan
Shylaja Sundararajan
updated the status to
under review
Shylaja Sundararajan
Hi Baji Patan,
Thnks for sharing feature request . Could you share additional details on the following
- what kind of failures needs ticket creation?
- are these tickets needs to be created during release time
- are multiple different services getting released and if yes , does the ticket needs to be created during failiure of any of the other tasks during release?
Thanks
Shylaja