- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday - last edited yesterday
Hi Everyone,
Just checking if anyone has successfully rolled out DevOps Change Velocity with ADO integration. We have been trying to get this working for several months now but encountering issue after issue which has resulted in multiple Hi tickets. Everything from permissions, PAT token and tool configuration issues, changes not auto closing, dates auto populating incorrectly etc.
Any success stories out there?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday - last edited yesterday
Hi @Manny T
I understand the frustration.
I recommend giving it one final attempt using the steps below.
Proposed rollout approach:
- If the integration is delivered as a plugin, it cannot be uninstalled.
- If it were a scoped application, you would have the option to uninstall it—but that isn’t the case here.
Recommendation:
Clone your sub-production instance (where the integration is currently configured) from the production instance to reset it to a clean state.
Resources for this integration:
DevOps Change Velocity - ServiceNow & Azure DevOps Integration
KB2523967 DevOps Change Velocity Integration with Azure DevOps Pipeline Execution Failing
https://www.youtube.com/watch?v=YzVo7ga-JlE&ab_channel=ServiceNowCommunity
https://www.youtube.com/watch?v=jstqIuw_0aA&ab_channel=ServiceNowDocumentation
https://www.youtube.com/watch?v=WXeJitCHDfA&ab_channel=ServiceNowDocumentation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday - last edited yesterday
Hi @Manny T
I understand the frustration.
I recommend giving it one final attempt using the steps below.
Proposed rollout approach:
- If the integration is delivered as a plugin, it cannot be uninstalled.
- If it were a scoped application, you would have the option to uninstall it—but that isn’t the case here.
Recommendation:
Clone your sub-production instance (where the integration is currently configured) from the production instance to reset it to a clean state.
Resources for this integration:
DevOps Change Velocity - ServiceNow & Azure DevOps Integration
KB2523967 DevOps Change Velocity Integration with Azure DevOps Pipeline Execution Failing
https://www.youtube.com/watch?v=YzVo7ga-JlE&ab_channel=ServiceNowCommunity
https://www.youtube.com/watch?v=jstqIuw_0aA&ab_channel=ServiceNowDocumentation
https://www.youtube.com/watch?v=WXeJitCHDfA&ab_channel=ServiceNowDocumentation
