Dentolize · Jira/Confluence QA Pipeline Walkthrough
On this pageThe one-linerWhere this is marketableMessaging pillarsWhat NOT to sayAssets you can pull from

For Marketing

First, the honest framing. This is an internal engineering-process change, not a product feature. It does not ship to dental clinics. You will almost never market this PR to customers. What follows is how to talk about it where it genuinely belongs — engineering-culture storytelling, careers, and the trust story behind Dentolize's quality.

The one-liner

"Every code change to Dentolize gets its own live copy of the app and an AI QA agent that plans and runs the tests — with a human QA lead approving every step in Jira."

Where this is marketable

1. Engineering brand / careers

This is a great "how we build" story for a careers page, an engineering blog, or a recruiting deck:

  • "AI-assisted, human-governed QA." We use AI to draft test plans and drive the browser, but a person edits the plan in Jira and signs off before anything is fixed. That's a mature, responsible take on AI in engineering — exactly what strong candidates want to hear.
  • "Every PR gets a real environment." Reviewers never argue over screenshots; they click the actual change. Combined with AI QA, it says we take quality seriously enough to automate it.

2. The trust / quality narrative (indirect, customer-facing)

Clinics hand Dentolize their patients' medical and financial data. You can, at a high level and without naming this PR, reinforce:

  • "Every change is tested on an isolated, disposable copy of the system before it reaches your clinic."
  • "Our quality process keeps a human reviewer in the loop on every release."

Keep it truthful and general — don't imply the AI is a certification or a guarantee.

Messaging pillars

PillarSay
Governed AIThe machine proposes; a human QA lead disposes. Required approval gates, not autopilot.
Real environmentsDisposable, per-change live sandboxes — not mocked, not staged-once.
Tools people already useQA lives in Jira and Confluence, where the team already works.
RestraintWe removed the "fully automatic" mode. We chose human oversight over speed.

What NOT to say

  • ❌ "Now available to customers." It's unreleased and internal.
  • ❌ "AI tests everything automatically." A human gates every phase; the fully-automatic option was removed.
  • ❌ "AI finds all the bugs." It drafts and runs test cases a human curates; it is an assistant, not a guarantee.
  • ❌ Anything implying the QA agent reviews the Jira/Confluence content inside this repo — that logic lives on separate infrastructure.

Assets you can pull from

  • The Feature Tour has real screenshots of the sandbox environment the agent drives.
  • The Overview has the clean four-phase table.
  • The human-in-the-loop story is in The Human QA Gates — the strongest, most differentiated angle.