Integrations
Connect the tools your team already uses, so Qalion AI can read from them and Qalion can file Jira issues.
The Integrations page
Click Integrations in the sidebar (Owners and Admins). It has three tabs: Overview, Servers and API keys. API keys have their own page in these docs.
Connected tools (MCP servers)
The Servers tab lists the tools you can connect over the Model Context Protocol (MCP):
| Group | Tool | How you connect |
|---|---|---|
| Source control | GitLab | Authorize with GitLab |
| Source control | GitHub | Personal access token |
| Source control | Bitbucket Cloud | Atlassian email and API token |
| Integrations | Jira | Authorize with Atlassian |
| Integrations | Notion | Authorize with Notion |
| Integrations | Linear | Authorize with Linear |
| Integrations | Sentry | Authorize with Sentry |
| Integrations | Figma | Personal access token |
- Click Connect on a tool. "Authorize with …" sends you to the tool to approve access, then back to Qalion.
- Test checks a connection and lists the tools it offers. The trash icon deletes it.
- Qalion AI can use the tools of your connections, for example to read a Jira ticket while it drafts test cases. Anything it would write to a connected tool waits for your approval on a "Write to connected tools" card. Credentials stay on Qalion's servers.
- A tool your Qalion deployment doesn't support shows as not enabled.
Jira
The Jira card has two separate options:
| Option | What it does | Setup |
|---|---|---|
| Read tickets while writing test cases | Lets Qalion AI read Jira, import tickets as requirements, and lets Coverage Sync from Jira | Authorize with Atlassian |
| File an issue when a test fails | Report to Jira from a run or a problem, and optionally file every failure automatically | Jira issue reporting settings |
To set up issue reporting, open Jira issue reporting settings:
1
Enter the Server URL (for example
https://your-team.atlassian.net), your Email and an Atlassian API token.2
Enter the Project key and choose the Issue type.
3
Optionally tick Report failures automatically: every failed result then opens an issue without anyone asking. On a large or flaky suite, that is a lot of issues.
4
Click Test connection, then Save.
Then use Report to Jira on an execution, Report or Create Jira ticket on a problem. A result or problem that already has an issue links to it instead of creating a second one.
Was this page helpful?