Creating Tickets
From one line to a ticket an engineer can build. Brief writes testable acceptance criteria into Jira, each tied to the decision, customer, or persona behind it.
-
01
One line in Jira
MER-2 arrived the way most tickets do: a title, a one-line description, no owner, no criteria.
Nobody reading it can say who needs it or what correct looks like.
Add industry filter to benchmark table
- Description
- Add industry filter to benchmark table.
- Assignee
- Unassigned
- Acceptance criteria
- None
-
02
Brief finds the context
The feature behind MER-2 already answers all three questions, with the evidence attached.
All three answers were already on the feature record.
Benchmark table in QBR export
Help account managers explain a customer account using relevant peer benchmarks. Use governed CDP data and Compass v2. Industry filtering is requested by the August advisory board.
- Who needs it?Built for
- Account manager
- Executive sponsor
- What problem does it solve?Research signals and a source quote
- Account managers need less manual benchmark preparation
- Eight relevant benchmarks with industry filters
“Twelve benchmarks is noise. Give me eight and let me filter by industry.”
- What does correct look like?Decisions that constrain it
- D-039Customer data comes through the CDP service
- D-040New charts and tables use Compass v2
- D-041QBR peer benchmark default
-
03
Written back to Jira
Seven testable criteria written into the MER-2 description.
Three wait on D-43, a proposal the PM has not approved.
Binding nowApplies regardless of D-43
- 1
Customer and account data comes only through the approved CDP service. No warehouse queries, no third-party enrichment.
D-039 · CDP-only customer data
- 2
New or modified chart and table components use Compass v2. Compass v1 is not extended.
D-040 · Compass v2
- 3
QBR exports keep the twelve-peer default. Eight is not authorized on this ticket.
D-041 · QBR peer benchmark default
- 4
The benchmarks table schema name stays unchanged.
D-042 · Q4 schema naming freeze
Only after D-43 is approvedA pending proposal, not a decision
- 5
Exports default to eight peer benchmarks instead of twelve.
D-43 · Proposed
- 6
A single-select industry filter narrows the peer set to one industry.
D-43 · Proposed
- 7
Neither change ships to production until the PM approves D-43.
D-43 · Proposed
- 1
-
04
Handoff in Slack
Brief posts the summary to #meridian-product in the PM's name.
The message says what binds, what waits, and what did not change.
Product Manager 5:08 PM
Correction: acceptance criteria added to MER-2.
- Binding now: CDP-only data, Compass v2 components, 12-peer default, unchanged schema names.
- D-43 (eight peers plus industry filter) still needs PM approval.
No Jira or decision changes were made.
Sent via Brief
Start with Jira and one product line
Brief writes the criteria from your own decisions and customer evidence, then hands the summary to your team.
- Acceptance criteriaAs filed: 0After Brief: 7
- Decisions citedAs filed: 0After Brief: 4
- Personas linkedAs filed: 0After Brief: 1
- Proposals flagged as pendingAs filed: 0After Brief: 1