Docs and test management

Confluence

Publish scan reports where your team keeps its docs

Teams plan

Publish any scan as a Confluence page under the space and parent page you pick: the site, the result and score, the open problems by severity, every problem worst first with its page, and a link back to the evidence. Good for release sign-offs, QA write-ups and anyone who doesn’t log in to ValiqAI.

Publishing is from the scan’s Share menu, one page per scan; publishing again opens the same page. ValiqAI uses the same Atlassian app as Jira but its own connection, asking only for Confluence access, so your Jira connection is untouched.

Connecting Confluence in ValiqAI, then what Confluence shows after a scan, and back to the results.

How it works

  1. A scan finishes. Scheduled, from CI, the CLI or the app.
  2. Publish from Share. One click makes a page under your chosen parent: the result, the counts and every problem.
  3. Read it in Confluence. Link it in a release ticket or a status update; it links back to the scan for the evidence.

Set up

In ValiqAI, open Integrations › Confluence in your workspace.

  1. Click Connect Confluence and approve ValiqAI for your Atlassian site.
  2. Pick the space and the parent page reports go under.
  3. Open a finished scan and choose Share › Publish to Confluence.

Plan

Confluence is on the Teams plan (Teams and Enterprise). A connection made before a plan change keeps working.

With AI tools

With the ValiqAI MCP server added to your AI coding tool, you can ask:

  • “Scan staging with ValiqAI before the release; I will publish the report to the release page.”
  • “Summarize the last ValiqAI scan of staging for a Confluence release note.”