delivered — dev work complete, proof condition not yet verified. done stays reserved for verified proof. Nothing else crosses the seam.
Setup
Import the blueprints
From the repo:
pb-to-jira and jira-to-pb. In Make: Create a new scenario → ⋯ → Import Blueprint.Create the webhooks
In each scenario, open the first module and create a new custom webhook. Copy both URLs.
Fill the placeholders
Scenario A (PB → Jira): your site URL (
YOUR_SITE.atlassian.net), project key, and a Basic auth value — base64(your-email:api-token) (create the token at id.atlassian.com → Security). Scenario B: your ProductBrain API key (Settings → API Keys).Point Jira at Make
Jira → Settings → System → Webhooks → new webhook with Scenario B’s URL, event Issue: updated. Optionally scope with JQL:
labels in ("pb-managed").How the linkage works
The issue carries two labels:pb-job-12 and pbp-my-project. Scenario B parses them — Jira Cloud webhooks deliver descriptions in ADF format, so labels are the reliable carrier. Don’t remove the pb- labels.
Why delivered, not done?
A completed ticket is a claim that work is finished. A ProductBrain job is a proof condition — something observable in the deployed product. The integration records the claim (delivered); verifying the proof and marking done stays with you or your agent.
Verified with live Make scenarios against payloads in Jira’s documented webhook shape; the first run on your Jira site is the final validation.

