Bugbot Coverage Status & Repo Enabled/Disabled Issue For Azure DevOps

[Todd_Barton]

Where does the bug appear (feature/product)?

Bugbot / Security Review Agent

Describe the Bug

After enabling bugbot on Azure DevOps repos and is cursor working on reviewing PRs, we return to /automations/from-cursor/bugbot and coverage is shown at zero and repos don’t show they’re enabled.

See screenshots…online dashboard doesn’t show any of this is enabled anymore. We can’t control certain things (i.e. Repository Rules) because the UI doesn’t think anything is enabled or an organization isn’t setup, but it is.

Also, we have no way to disable/turn-off cursor from executing PR reviews for a repos we’ve enabled other than disabling the user in our devops system, which would disable all of the repos for PR reviews.

We understand the DevOps integration is limited use, but these seem to be basic required controls.

Steps to Reproduce

After enabling bugbot on Azure DevOps repos, return to /automations/from-cursor/bugbot and coverage is shown at zero and repos don’t show enabled.

Expected Behavior

I would expect to see the coverage number to be correct and the repos we have enabled would have the toggle on (see screen shots) and we could turn off if needed.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

3.17.21 (user setup)

Additional Information

I’ve enabled and connected Azure DevOps to cursor for BugBot. I’ve followed the instructions at Azure DevOps | Cursor Docs including giving service principal access to our organization and proper repo rights (project administrator) to the cursor principle/user.

Does this stop you from using Cursor

No - Cursor works, but with this issue

[mohitjain (Mohit)]

Hey Todd
This is just a display issue on the dashboard, not anything on your end. Your repos are still enabled and Bugbot is actively reviewing your PRs (your “48 PRs reviewed” confirms it) - the Automations page just isn’t reading back the per-repo state for Azure DevOps, so toggles show off and coverage reads 0%. Nothing you’ve configured is lost.

It’s not intended behavior and it’s an issue we’re tracking. To turn a repo’s reviews off in the meantime: toggle it twice in the same view without refreshing (the first click sends “enable” since it shows off, the second sends “disable”). If that doesn’t stick, email [email protected] with the repo name and we’ll see if we can do something on our end to disable it. I’ll post here when there’s an update.