> For the complete documentation index, see [llms.txt](https://learning.contextqa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learning.contextqa.com/integrations/integrations.md).
# Integrations Overview
A guide to all the systems ContextQA connects with, including bug trackers, CI/CD pipelines, project management tools, and notification systems.
{% hint style="info" %}
**Who is this for?** SDETs, developers, and engineering managers who need to connect ContextQA to their existing CI/CD pipelines, bug trackers, and notification systems.
{% endhint %}
ContextQA is designed to fit into existing engineering workflows rather than replace them. The integrations in this section let you connect your test results to the tools your team already uses for project tracking, deployment, and communication.
## Quick answer
ContextQA integrations connect requirements, test execution, notifications, and defect reporting to the delivery tools a team already uses. Portal plugins are configured from **Integrations & Plugins**; CI/CD guides explain how to prepare approved test-plan quality gates; authenticated MCP tools let compatible AI agents orchestrate supported workflows. These are related surfaces, but they do not imply one interchangeable authentication or API contract.
## What this page covers
Open **Integrations & Plugins** in the ContextQA sidebar to configure portal integrations. Find a card in **All Plugins** or its category, select **View Details**, and open **Config**. Categories include Bug Reporting, Product Management, Test Lab, and CI/CD.
## Check connection health before depending on an integration
Connected GitHub, GitLab, Linear, and Slack cards can show **Reconnect needed** when the provider authorization or installation is no longer available. Reconnect the intended account, or disconnect it deliberately before connecting a different account. A completed provider authorization can also return a clear cancelled, approval-requested, expired, or save-failed outcome instead of leaving the connection state ambiguous.
After reconnecting:
1. Confirm the provider account or workspace shown on the integration details page.
2. Confirm the eligible repositories, projects, or Slack workspace.
3. Run one controlled workflow that uses the connection.
4. Open the resulting ContextQA link and verify that it resolves to the same workspace and run.
Disconnecting a source provider can remove its active repository or project registrations and stop new code-analysis or change-impact work. Historical analysis remains a record of what happened at the time; review the confirmation dialog before disconnecting.
***
## Bug trackers and issue managers
| Integration | Category | What it does |
| -------------------- | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Jira** | Bug Report | Generate test cases from Jira tickets; create Jira bug reports from failing tests; view execution status in the Jira sidebar panel |
| **Azure DevOps** | Requirements and Bug Report | Generate tests from Azure Boards work items and create defects from failed runs with reproduction evidence |
| **FreshRelease** | Bug Report | Push test failure details to FreshRelease issues |
| **Mantis** | Bug Report | Create Mantis Bug Tracker issues from failing test cases |
| **YouTrack** | Bug Report | Create YouTrack issues with execution evidence attached |
| **BackLog** | Bug Report | File Nulab BackLog issues from ContextQA test results |
| **BugZilla** | Bug Report | Create Bugzilla bug entries from ContextQA failures |
| **ContextQA Plugin** | Bug Report | Browser-based test recorder and issue capture plugin |
***
## Project management and ALM tools
| Integration | Category | What it does |
| ----------- | ------------------ | ------------------------------------------------------------------------------- |
| **Linear** | Product Management | Generate test cases from Linear issues; create Linear issues from test failures |
| **Trello** | Product Management | Create Trello cards from test failures; link test results to existing cards |
| **ClickUp** | Product Management | Push test failures to ClickUp tasks; generate tests from ClickUp tickets |
| **Zepel** | Product Management | Link test runs to Zepel sprints; create defect items from failures |
***
## CI/CD pipelines
Open a test plan and select **CI / CD** to review the integration targets exposed by the current production workspace. The page lists GitHub, GitLab, Bitbucket, Azure DevOps, CircleCI, Codeship, Bamboo, Jenkins, AWS, TravisCI, and Generic shell. It also describes **Start Test Plan** and **Check Status** REST operations.
{% hint style="warning" %}
The verified production page does not display public REST endpoint paths. These guides cover safe pipeline preparation and quality-gate design, but do not publish copy-and-paste calls based on private portal traffic. Use an endpoint contract only when it is displayed in your workspace or provided through an official ContextQA reference.
{% endhint %}
| Integration | What it does | Guide |
| ------------------- | ---------------------------------------------------------------------------------------------- | ------------------------------------------------- |
| **GitHub Actions** | Prepare repository secrets, variables, triggers, and branch protection for a plan quality gate | [GitHub Actions](/integrations/github-actions.md) |
| **Azure Pipelines** | Prepare secure variables and a deployment-stage quality gate | [Azure DevOps](/integrations/azure-devops.md) |
| **Jenkins** | Prepare Jenkins credentials and a test-plan gate | [Jenkins](/integrations/jenkins.md) |
| **GitLab CI** | Prepare protected variables and a merge-request gate | [GitLab CI](/integrations/gitlab-ci.md) |
| **CircleCI** | Prepare a Context, workflow trigger, and approval gate | [CircleCI](/integrations/circleci.md) |
Each guide separates verified portal behavior from external pipeline configuration that depends on a published API contract.
***
## Notification systems
| Integration | Category | What it does |
| ------------------- | ------------- | ------------------------------------------------------------------------------------------------------ |
| **Slack** | Notifications | Connect a Slack workspace, choose the approved channel, and send linked test or workflow notifications |
| **Microsoft Teams** | Notifications | Send test execution results and failure notifications to Teams channels |
| **Google Chat** | Notifications | Send test result notifications to Google Chat spaces via webhook |
***
## Security and test infrastructure
| Integration | Category | What it does |
| ------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------- |
| **Azure Key Vault** | Secrets Management | Retrieve test credentials and secrets from Azure Key Vault at execution time, avoiding hardcoded values in test steps |
| **Private Grid** | Test Lab | Execute tests on your own on-premises device grid rather than the ContextQA cloud infrastructure |
***
## Integration summary
ContextQA provides portal-managed plugin integrations plus CI/CD preparation guides for common external pipeline systems.
**Portal integrations** (**Integrations & Plugins**):
| Category | Count | Integrations |
| ------------------ | ----- | --------------------------------------------------------------------------------------- |
| Bug Report | 8 | Jira, Azure DevOps, FreshRelease, Mantis, YouTrack, BackLog, BugZilla, ContextQA Plugin |
| Product Management | 4 | Linear, Trello, ClickUp, Zepel |
| Notifications | 3 | Slack, Microsoft Teams, Google Chat |
| Secrets / Infra | 2 | Azure Key Vault, Private Grid |
**CI/CD preparation guides**:
| Category | Count | Integrations |
| -------- | ----- | ------------------------------------------------------------- |
| CI/CD | 5 | GitHub Actions, Azure Pipelines, Jenkins, GitLab CI, CircleCI |
Plugin categories in the UI:
* **Bug Report** — all defect tracker integrations
* **Test Lab** — Private Grid and device farm connectors
* **Product Management** — ALM and project tool integrations
***
## MCP server
The ContextQA MCP server exposes the platform's core capabilities as callable tools for authenticated MCP hosts. Relevant tools for integrations include:
* `execute_test_plan` — trigger a test plan by ID
* `execute_test_case` — run a single test case
* `get_execution_status` — poll an execution for its current state
* `create_defect_ticket` — create a bug report in Jira or Azure DevOps
* `generate_tests_from_jira_ticket` — generate test cases from a Jira or ADO ticket URL
* `generate_tests_from_linear_ticket` — generate test cases from a Linear issue
* `get_test_case_results` — retrieve results for a completed run
See the [MCP Server reference](/mcp-server/overview.md) for full tool documentation.
***
## In this section
* [Jira](/integrations/jira.md) — full Jira integration setup and usage
* [Azure DevOps](/integrations/azure-devops.md) — Azure Boards requirement generation, defect reporting, and Azure Pipelines integration
* [GitHub Actions](/integrations/github-actions.md) — running ContextQA tests in GitHub Actions workflows
* [Jenkins](/integrations/jenkins.md) — triggering test plans from a Jenkinsfile and failing builds on test failures
* [GitLab CI](/integrations/gitlab-ci.md) — triggering test plans from `.gitlab-ci.yml` and failing pipeline stages on test failures
* [CircleCI](/integrations/circleci.md) — triggering test plans from a CircleCI `config.yml` and failing workflows on test failures
* [Slack](/integrations/slack.md) — configuring Slack notifications for test events
* [Webhooks](/integrations/webhooks.md) — sending test results to any HTTP endpoint for custom integrations
***
## Execution Evidence
The following recording is from a live ContextQA execution demonstrating the integrations workflow:
***
## FAQs
Where do I find the integrations configuration in ContextQA?
Open **Integrations & Plugins** in the left sidebar. Find the integration in **All Plugins** or its category, select **View Details**, and open **Config**.
Can I connect multiple bug trackers at the same time?
Yes. You can configure multiple bug reporting integrations simultaneously (for example, both Jira and Azure DevOps). Each can be enabled or disabled independently.
Does the CI/CD integration require the MCP server?
No single transport is implied by the CI/CD tab. An authenticated MCP host can use `execute_test_plan`. A REST-based pipeline must use the current public endpoint contract provided for its workspace. Do not translate private portal calls into a public integration.
{% hint style="info" %}
**Connect ContextQA to your CI/CD pipeline in 15 minutes** [**Book a Demo →**](https://contextqa.com/book-a-demo/?utm_source=learning.contextqa.com\&utm_medium=referral\&utm_campaign=docs_demand_gen\&utm_content=integrations_overview)
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://learning.contextqa.com/integrations/integrations.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.