# Integrations Overview
{% 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.
All integrations are configured via **Settings → Plugins** in the ContextQA sidebar. Integrations are grouped into four categories: Bug Reporting, Test Lab, Product Management, and CI/CD.
***
## Bug trackers and issue managers
| Integration | Category | What it does |
| -------------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Jira** | Bug Reporting | Generate test cases from Jira tickets; create Jira bug reports from failing tests; view execution status in the Jira sidebar panel |
| **Azure DevOps** | Bug Reporting | Create Azure Boards work items from test failures; attach reproduction steps and screenshots automatically |
| **FreshRelease** | Bug Reporting | Push test failure details to FreshRelease issues |
| **Mantis** | Bug Reporting | Create Mantis Bug Tracker issues from failing test cases |
| **YouTrack** | Bug Reporting | Create YouTrack issues with execution evidence attached |
| **BackLog** | Bug Reporting | File Nulab BackLog issues from ContextQA test results |
| **BugZilla** | Bug Reporting | Create Bugzilla bug entries from ContextQA failures |
| **ContextQA Plugin** | Bug Reporting | 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
| Integration | Category | What it does |
| ------------------- | -------- | ---------------------------------------------------------------------------------------------------- |
| **GitHub Actions** | CI/CD | Trigger ContextQA test plans on push or pull request events; report results as a GitHub check status |
| **Azure Pipelines** | CI/CD | Run ContextQA test plans as a step in an Azure DevOps pipeline |
| **Private Grid** | Test Lab | Execute tests on your own on-premises device grid rather than the ContextQA cloud infrastructure |
CI/CD integrations use the ContextQA MCP server or REST API to start test plan executions and poll for results.
***
## Notification systems
| Integration | Category | What it does |
| ------------------- | ------------- | --------------------------------------------------------------------------------- |
| **Slack** | Notifications | Send test run summaries and critical failure alerts to Slack channels via webhook |
| **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 secrets
| 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 |
***
## Integration summary
ContextQA supports **17 integrations** across 5 categories:
| Category | Count | Integrations |
| ------------------ | ----- | --------------------------------------------------------------------------------------- |
| Bug Reporting | 8 | Jira, Azure DevOps, FreshRelease, Mantis, YouTrack, BackLog, BugZilla, ContextQA Plugin |
| Product Management | 4 | Linear, Trello, ClickUp, Zepel |
| CI/CD | 2 | GitHub Actions, Azure Pipelines |
| Notifications | 3 | Slack, Microsoft Teams, Google Chat |
| Secrets / Infra | 1 | Azure Key Vault, Private Grid |
All integrations are configured at **Settings → Plugins**. 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
* **CI/CD** — pipeline trigger integrations
***
## MCP server
The ContextQA MCP server exposes the platform's core capabilities as callable tools that can be invoked from AI agents, CI scripts, or any MCP-compatible host. 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](https://github.com/indivatools/gitbooks-docs/blob/main/docs/mcp-server/README.md) for full tool documentation.
***
## In this section
* [Jira](https://learning.contextqa.com/integrations/jira) — full Jira integration setup and usage
* [Azure DevOps](https://learning.contextqa.com/integrations/azure-devops) — Azure Boards and Azure Pipelines integration
* [GitHub Actions](https://learning.contextqa.com/integrations/github-actions) — running ContextQA tests in GitHub Actions workflows
* [Slack](https://learning.contextqa.com/integrations/slack) — configuring Slack notifications for test events
***
## 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?
All integrations are configured at **Settings → Plugins** in the left sidebar. Plugin categories in the UI are: Bug Report, Test Lab, Product Management, and CI/CD.
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. CI/CD integrations can use either the MCP server or the ContextQA REST API to trigger test plans and poll for results. See the [MCP Server reference](https://github.com/indivatools/gitbooks-docs/blob/main/docs/mcp-server/README.md) for MCP-based integration, or the API documentation for REST-based integration.
{% hint style="info" %}
**Connect ContextQA to your CI/CD pipeline in 15 minutes** [**Book a Demo →**](https://contextqa.com/book-a-demo/)
{% endhint %}