Logo
      SCHEDULE A CALL
      hero

      AI ASSISTANT FOR AZURE DEVOPS - TECHNICAL SUPPORT

      Extension type: Azure DevOps Services (cloud)

      • Scopes:
      • Boards (Work Items)
      • Repos (Pull Requests)
      • Test Plans (Runs/Results)

      Generate

      Acceptance Criteria

      KEY

      FEATURES

      Generate

      Test Cases

      Create Bug from

      Test Case Step

      AI Code Review

      BYOK

      (Bring Your Own Key)

      GETTING STARTED

      01

      Install from Visual Studio Marketplace → select your organization.

      02

      Open the extension hub and switch to the Setup tab to configure BYOK (only if you have the BYOK license).

      03

      Open the Billing tab and activate the Free trial for your organization (or applicable projects).

      FEATURES

      FEATURES

      Generate Acceptance Criteria (Boards)

      • Action on PBI/User Story work item: AI → Generate Acceptance Criteria.
      • Output styles: Bulleted or Gherkin (Given/When/Then).
      • Inserts content into the work item’s Acceptance Criteria field or a checklist.

      Generate Test Cases (Boards/Test Plans)

      • From a Story/Product backlog item/Feature: AI → Generate Test Cases.
      • Creates test cases (steps & expected results) and adds them to a selected test plan/test suite.

      Create Bug from Test Case Step (Test Plans)

      • From Test Plans → Runs/Results: AI → Create Bug from Failure.
      • Preloads failing step text, actual vs expected, evidence (screenshots/video), environment/build.
      • Links the bug to the Result/Run and optionally to the Story/PBI.

      AI Code Review (Repos → Pull Requests)

      • Run AI → Review Changes on a PR.
      • Posts inline comments or a summary with suggestions (security, performance, readability profiles).

      BYOK (Bring Your Own Key) — Setup tab

      Configure your own Azure OpenAI (or other supported LLM) on the Setup tab of the extension.

      Fields

      Endpoint URL – Your Azure OpenAI endpoint (e.g., https://<resource-name>.openai.azure.com).

      Deployment Name – The deployed model name (e.g., o4-mini).

      API Key – Your provider key.

      Buttons

      Save – Persists the configuration for the current project.

      Check Connectivity – Verifies that the endpoint, deployment, and key are valid.

      Delete Configuration – Removes the stored key and settings for the project.

      Security & Storage

      Keys are stored securely in the project context; only authorized users of the extension can use them.

      For tighter control, restrict who can access the extension and who can open the Setup tab via project permissions.

      Data Filtering and Calibration

      Implementation of specific algorithms, such as Data Forest Classifier, for data refinement.

      Manage tab — enable/disable by project

      Use the Manage tab to control which projects can use the extension.

      How it works

      • Select a project from the dropdown and click Enable.
      • The project appears under Enabled Projects with a Disable button.
      • Toggle Hide extension for disabled projects to prevent the extension UI from appearing in projects that aren’t enabled.

      Permissions

      • Only Project Administrators (or users granted the extension’s admin permission) can enable/disable projects.

      USAGE

      USAGE

      Acceptance Criteria

      Boards → open Story/PBI → AI → Generate Acceptance Criteria → review → Save.

      Test Cases

      Boards/Test Plans → AI → Generate Test Cases → choose test plan/test suite → Generate.

      Create Bug from Failure

      Test Case/Test Plans→ Create bug from test case → AI → Create Bug → Save.

      AI Code Review

      Repos → Pull Requests → AI assistant tab→ AI code review→ comments/summary posted to the PR.

      DATA HANDLING & SECURITY

      DATA HANDLING & SECURITY

      icon

      BYOK

      Your keys remain in your organization; the extension reads them at runtime.

      icon

      Data minimization

      Optional redaction of secrets/PII patterns before sending prompts.

      icon

      Auditability

      Generated content is saved as standard Azure DevOps artifacts (work item history, PR comments).

      icon

      Rate limits

      Peruser and perproject throttling to prevent abuse.

      TROUBLESHOOTING

      Buttons not visible

      Confirm installation, user permissions, and that the project is enabled.

      Unauthorized

      Verify project permissions for Work Items/Test Plans/Repos.

      AI request failed

      Check BYOK keys/endpoint and network rules; reduce context size (very large PRs/descriptions).

      Missing attachments in bug

      Ensure evidence is saved to the test result and project attachment limits are not exceeded.

      KNOWN ISSUES

      No custom buttons inside the Manual Test Runner panel (platform limitation). Use actions in Test case Work Items.

      FAQ

      FAQ

      Support

      Email: ai-assistant@qubiz.com

      SLA: Initial response within 1-3 business days

      Privacy

      Policy: https://example.com/privacy

      Data retention: No persistent storage by the extension; artifacts are created inside your Azure DevOps project.

      License

      EULA: https://example.com/license

      icon

      Subscribe to our newsletter

      Stay up to date with the latest technology news:
      socialsocialsocialsocial
      COMPANY
      EXPERTISE
      INSIGHTS
      LEGAL

      Copyright Qubiz 2025. All rights reserved.

      About Us
      Our Story
      Leadership
      What We Do
      Services
      Focus Areas
      Industries
      Technologies
      Success Stories
      Project Timeline
      Blog
      Privacy
      Cookie Policy
      Candidate Cookie Policy
      Impressum
      Terms & Conditions
      Logo