Claude Code Guide
বাংলায় পড়ুন

15 min / intermediate / 5 steps

Turn Meeting Notes into Jira Tickets

Paste your messy meeting notes. Get structured tickets with acceptance criteria. Never transcribe by hand again.

Every PM has been there. You walk out of a meeting with a page of messy notes and spend the next hour turning them into Jira tickets. Let's automate that. You'll create a skill that takes raw meeting notes and outputs clean, structured tickets ready to file.

follow along in

You need: A Claude account. Open claude.ai in a browser, or the Claude desktop app.

  1. step 01 / 05

    Set up a CLAUDE.md with PM context

    Start by giving Claude some context about your work. You don't need much, just enough so it knows what kind of tickets you create.

    Prompt
    I want to turn meeting notes into Jira tickets. Before I paste notes, here's my context: I'm a PM for a SaaS app, web + mobile. Tickets go in Jira project KEY. Story points: 1, 2, 3, 5, 8. Teams: frontend (React), backend (Node), mobile (React Native). Always include acceptance criteria as checkboxes.

    what you should see

  2. step 02 / 05

    Create the meeting processor skill

    This skill tells Claude exactly how to parse meeting notes. It extracts action items, decides who owns them, estimates effort, and formats them as tickets.

    Prompt
    Here's how I want you to process meeting notes into tickets: 1. Extract every action item and decision 2. Group related items into one ticket each 3. Estimate story points (1/2/3/5/8) based on complexity 4. Assign team labels (frontend/backend/mobile/design) 5. Write at least 3 acceptance criteria per ticket 6. Flag vague items as "needs clarification" Is that clear?

    what you should see

  3. step 03 / 05

    Paste messy meeting notes

    Here's the real test. Paste some actual messy meeting notes (or use these sample ones) and watch Claude turn chaos into structure.

    Prompt
    Process these meeting notes into tickets: Sprint planning March 29. Sarah mentioned checkout is broken on mobile, users can't tap pay. Also add apple pay before Q2. Jake said API is too slow on product listing - 3 seconds, add caching. Marketing wants spring sale banner on homepage by friday. Someone should fix onboarding step 3 dropoff.

    what you should see

  4. step 04 / 05

    Review the structured output

    Claude gives you fully formed tickets with types, story points, labels, and acceptance criteria. Each one is ready to paste into Jira. No more staring at your notes trying to remember what was decided.

    Prompt
    That's actually really good. How long would this have taken manually?

    what you should see

  5. step 05 / 05

    Optional: Connect an MCP for auto-creation

    If you want to go further, you can connect a GitHub or Linear MCP server so Claude can create the tickets directly. No copy-paste needed.

    Prompt
    Can Claude actually create the Jira tickets directly, not just write them out?
    json
    # Add to your .mcp.json to enable GitHub Issues:
{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_TOKEN": "your-token-here"
      }
    }
  }
}

    what you should see

go deeperExplore the full PM workflow guide

Tell someone what you built

Just finished "Turn Meeting Notes into Jira Tickets" on Claude Code Guide. Took about 15 min, and it's free: https://claudecodeguide.dev/tutorials/meeting-to-jira

Share on LinkedIn

New guides, when they ship

One email, roughly weekly. CLAUDE.md templates, workflows I actually use, and the cut-for-length stuff that does not make the public guides. One-click unsubscribe.

Or read Product Field Notes, the Substack