Use Jira with an AI Browser for Meeting Prep

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.