Beta

Use Jira with an AI Browser for Meeting Prep

Run meeting prep in Strawberry using Jira as one of the inputs. Specific surfaces, example prompt, real output, and tradeoffs vs alternatives.

If you use Jira and you regularly need to prepare for a meeting, the bottleneck is usually the same: Jira holds part of the context, but meeting prep also needs signals that live outside it - on the public web, in LinkedIn, in news, in other connected apps. Strawberry is built to combine the Jira context with the rest of the browser, and run the full workflow as a companion you can re-trigger every week.

This page describes specifically how Strawberry handles meeting prep when Jira is one of the inputs. It names the Jira surfaces involved, the signals the workflow actually needs, an example prompt you can paste, and what a good output looks like.

The job a AE, founder, CSM, or anyone with a calendar full of calls is trying to do

The goal of meeting prep is to produce a one-page brief for each upcoming meeting so the person walks in informed and time isn't wasted. The success metric is concrete: subjective - the meeting feels productive; objective - notes/next-step ratio is high. That definition matters because it shapes what Jira needs to contribute to the workflow.

What signals meeting prep actually needs

For each signal below, here is whether Jira can contribute directly or whether Strawberry has to find it via the browser:

  • Attendee LinkedIn snapshots (role, tenure, mutuals) - Jira does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
  • Company recent news (funding, hires, product) - Jira does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
  • Last touchpoint in the CRM - Jira does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
  • Any open opportunities or support cases - Jira does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
  • Agenda or context from the calendar event description - Jira does not contain this directly. Strawberry uses the browser plus public sources to fetch it.

What Strawberry can do inside Jira

Strawberry can run JQL queries, summarize sprint status, and create issues from external context.

Jira surfaces Strawberry uses for this workflow: issues, epics, sprints, boards, JQL queries.

How Strawberry runs meeting prep with Jira

  1. Strawberry opens the Jira issues that contains the relevant context.
  2. The companion pulls related context from Jira (epics, history, attached files) where it exists.
  3. For the parts Jira does not store, Strawberry uses the browser - web search, LinkedIn, news, the prospect's website.
  4. Strawberry synthesises the output in the shape this workflow needs: A 250-400 word brief.
  5. A human reviews before any external action (send, update, post). Then the approved output is saved back to Jira or your system of record.

Example Strawberry prompt

Paste this in a new Strawberry chat with Jira connected. Adjust the specifics to your actual ICP, role, or topic.

Read this Jira issues and any linked context.
Then run a full meeting prep workflow on it. Use the browser to fill any gaps not in Jira.
Return the output in the shape we use for meeting prep: A 250-400 word brief: attendees, company snapshot, last touch, suggested agenda, 3 questions to ask.
Do not send anything externally. Save the draft to me to review.

What a good meeting prep output looks like

Here is what a finished output for meeting prep should look like in practice. The specifics will change for your use case, but the shape should look similar:

  • Meeting: 14:00 Thursday with Anna Lindqvist (VP Marketing, Voi) and Erik Nilsson (Head of Growth)
  • Last touch: warm intro from Marcus on May 14, no reply since
  • Company news: Germany pullout announced May 28; hired 4 paid acquisition managers in Q1
  • Suggested agenda: 1) Their take on Germany decision, 2) Where retention sits in 2026 priorities, 3) Show 90-sec demo of win-back loop
  • Three questions: How is the team structured post-pullout? What's the budget cycle? Who owns retention KPIs?

Why Jira for this, and where to use a different tool

Jira is strong for this workflow because Strawberry can run JQL queries, summarize sprint status, and create issues from external context.

Where Jira falls short Jira custom fields and permission schemes are notoriously project-specific; Cloud vs Data Center auth differs.

Consider also a CRM for go-to-market follow-up.

Common mistakes when running meeting prep

  • Generic bios instead of role-specific context
  • Missing the most recent news that the prospect would expect you to know
  • No link back to the prior conversation thread

Connecting Jira to Strawberry

Atlassian OAuth - Jira + Confluence share the same connection. Once connected, the companion can read the surfaces above without re-authenticating, and any write action still requires explicit human approval the first time the workflow runs.

Caveats

Do not let any AI agent send emails, update CRM records, or change shared systems without a clear approval step. Strawberry is strongest when the workflow combines browser context with connected-app context and a human review for sensitive actions.

How Jira + Strawberry runs meeting prep

1 Jira

Read

Open the relevant Jira issues; pull related context.

2 Browser

Augment

Use the browser, LinkedIn, news, and other connected apps for signals outside the CRM/tool.

3 Output

Compose

Synthesise into the meeting prep shape: A 250-400 word brief.

4 Human

Approve

Human reviews before any external action; approved output is saved back.

FAQ - Jira + AI browser for meeting prep

Can Strawberry do meeting prep entirely inside Jira?

No, and that is the point. meeting prep needs signals Jira does not store - public web, LinkedIn, news, other apps. Strawberry combines Jira with the browser, which is where the real value comes from.

Does Jira need to be the primary CRM or system of record?

Not necessarily. Jira can be one input among several. Strawberry can read it as context even if your primary system of record is somewhere else.

What permissions do I need on Jira?

Read access to the surfaces you want Strawberry to use (issues, epics, sprints). Write permissions are only needed if you want Strawberry to update Jira after a human approves the change. Atlassian OAuth - Jira + Confluence share the same connection.

What is the realistic success metric for meeting prep?

subjective - the meeting feels productive; objective - notes/next-step ratio is high - that is the target Strawberry helps you hit, not the only thing it measures.

What is the biggest mistake to avoid?

Generic bios instead of role-specific context.

Run meeting prep in 10 minutes with Strawberry and Jira

  1. Open Jira

    Connect Jira so Strawberry can read issues, epics, sprints, boards, JQL queries, custom fields and combine them with the rest of the brief. Pin the specific records or views you want to start from so the agent does not drift.

  2. Tell Strawberry the brief

    Drop the prompt below. Replace the placeholder with the actual AE, founder, CSM, or anyone with a calendar full of calls target - one name, one URL, or one Jira reference is enough. Keep the goal explicit: produce a one-page brief for each upcoming meeting so the person walks in informed and time isn't wasted

  3. Let it gather signals

    Strawberry pulls attendee LinkedIn snapshots (role, tenure, mutuals) and company recent news (funding, hires, product), then layers public web sources in parallel. You should see citations next to each fact - that is the audit trail. Watch the Jira side: Jira custom fields and permission schemes are notoriously project-specific; Cloud vs Data Center auth differs

  4. Review before write-back

    Output lands in the shape you asked for: A 250-400 word brief: attendees, company snapshot, last touch, suggested agenda, 3 questions to ask. Read it once. Fix anything off. The success metric is subjective - the meeting feels productive; objective - notes/next-step ratio is high - if the draft does not hit that bar, send it back with a one-line correction.

  5. Save it as a routine

    If you will prepare for a meeting this again next week, click Save as routine. Pick a cadence (daily, weekly, on-trigger). Strawberry re-runs the whole flow on schedule and pings you when the new output is ready.

Paste-ready prompt for meeting prep with Jira

You are helping me prepare for a meeting meeting prep. Use Jira as one input and the public web for the rest.

Target: [paste one AE, founder, CSM, or anyone with a calendar full of calls target here - a Jira reference, a name + company, or a URL]

Goal: produce a one-page brief for each upcoming meeting so the person walks in informed and time isn't wasted

Signals to gather:
- attendee LinkedIn snapshots (role, tenure, mutuals)
- company recent news (funding, hires, product)
- last touchpoint in the CRM
- any open opportunities or support cases
- agenda or context from the calendar event description

Output shape: A 250-400 word brief: attendees, company snapshot, last touch, suggested agenda, 3 questions to ask

Rules:
- Cite every fact with a link or a Jira reference. If you cannot find a signal, say so explicitly rather than guessing.
- Do not invent specifics. Use real, dated signals from the last 90 days where possible.
- If a fact would change the outcome and is missing, pause and ask me before writing the final output.

When the output is ready, surface it in this chat. Do not write back to Jira or send anything externally until I approve.

Paste this into Strawberry's chat field. Replace the target placeholder before running.

When Jira + Strawberry is the right combo for meeting prep

Jira is the enterprise issue tracker. Strawberry can run JQL queries, summarize sprint status, and create issues from external context. For meeting prep specifically, that means the agent already has issues, epics, sprints, boards, JQL queries, custom fields as starting context - you do not need to brief it from scratch.

When it is NOT a fit

  • You need a single number, not a synthesised brief. A SQL query against your warehouse is faster.
  • The decision is happening in the next 60 seconds. The agent is fast but it is not instant; for hard real-time use, do it manually.
  • The Jira data you would feed in is stale or wrong. Garbage in, confident garbage out.

Three mistakes to avoid

  1. generic bios instead of role-specific context
  2. missing the most recent news that the prospect would expect you to know
  3. no link back to the prior conversation thread

Honest tradeoff

Jira custom fields and permission schemes are notoriously project-specific; Cloud vs Data Center auth differs. If you are running this at scale (10+ briefs per day), batch the inputs and let Strawberry process them as a routine instead of one-by-one prompts - cheaper per brief and the output stays consistent.

What a real output looks like

Meeting: 14:00 Thursday with Anna Lindqvist (VP Marketing, Voi) and Erik Nilsson (Head of Growth),Last touch: warm intro from Marcus on May 14, no reply since,Company news: Germany pullout announced May 28; hired 4 paid acquisition managers in Q1,Suggested agenda: 1) Their take on Germany decision, 2) Where retention sits in 2026 priorities, 3) Show 90-sec demo of win-back loop,Three questions: How is the team structured post-pullout? What's the budget cycle? Who owns retention KPIs?
Download