Skip to main content
A new ProductBrain Job creates a Jira issue (Story by default. Change the issuetype in the blueprint). That container reaching a done status category marks the job delivered, dev work complete, proof condition not yet verified. done stays reserved for verified proof. Nothing else crosses the seam.

​
Setup

1

Import the blueprints

From the repo: pb-to-jira and jira-to-pb. In Make: Create a new scenario → ⋯ → Import Blueprint.
2

Create the webhooks

In each scenario, open the first module and create a new custom webhook. Copy both URLs.
3

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).
4

Point ProductBrain at Make

5

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").
6

Turn both scenarios on

Create a job in ProductBrain, Jira issue appears. Complete it, the job shows delivered.

​
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.