Connect Azure Repos with DevRev to keep your work seamlessly in sync across both systems. This snap-in ensures that issue tracking and status updates are real-time and driven by code activity. Widely adopted by organizations, Azure Repos for DevRev eliminates the need for manual issue management by linking DevRev issues directly with Git activity.
Use this snap-in if you want to reduce overhead and let automation manage your issues. It helps developers stay focused by automating issue creation and status updates. This snap-in is especially valuable if you have ever:
Delivered a hotfix without an issue to track it
Spent time updating your team on issue statuses
Felt issue management was a distraction from real work
Whether your team manually links issues to Git activity or prefers a hands-off approach, this snap-in adapts accordingly. It honors existing links using issue IDs in branches, commits, or PRs. If no links are provided, it automatically creates and manages issues for you, ensuring visibility and accountability across the team.
Features
- Automatic status updates
Mentions of DevRev issues in Azure Repos (via branch names, commit messages, or PR titles) automatically associate activity with the corresponding issue. This enables seamless status updates like transitioning from In Development to In Review and eventually Closed.
- Auto create issues from Azure Repos branches
If no issue is linked when a branch is created, an issue is auto-generated and tracked. The issue status transitions based on Git activity and can be customized to close automatically when PRs are merged.
- Auto create issues from Azure Repos PRs
New PRs without a linked DevRev issue automatically create autonomous issues. These issues are updated with PR activity and descriptions, and statuses transition based on merge events.
- Enrich and relate autonomous issues
Autonomous issues are enriched with PR titles and descriptions. They can also be linked as child issues to parent work-items mentioned in the PR body.
- Automatic PR reminders
When a PR remains inactive for a specified period (max_inactive_days), reminders are posted in related DevRev issues. These reminders apply to both manually and autonomously created issues.