Generate a retrospective automatically when a Jira epic closes

When a Jira epic is marked done, this pulls the comments and writes a retrospective document for you.

How the work actually flows

A straight line.

Pattern: Sequence (1)

flowchart TD trig>"Jira epic marked done"]:::trig s0["pull epic comments"]:::svc s1["organize into timeline"]:::task s2["AI drafts retrospective"]:::task s3[("save document to drive")]:::store s4["link retro on epic"]:::svc trig --> s0 s0 --> s1 s1 --> s2 s2 --> s3 s3 --> s4 out[/"retrospective linked to epic"/]:::out pay{{"lessons captured without manual writing"}}:::pay s4 --> out out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepAn outside serviceA record or sheetResultPayoff
Build size
Advanced

A larger build with multiple systems, AI reasoning, and custom rules.

Business functions
AI Agents & Autonomous SystemsReporting & AnalyticsProject & Task ManagementFile & Cloud Storage
Connects
JiraGoogle DriveOpenAI

The problem it solves

Writing a retrospective after a big project wraps up means digging back through weeks of Jira comments to remember what happened. That work often gets skipped, so the lessons never get written down.

Who it fits

Project managers and teams who use Jira and want a written retro for every completed epic.

How it works

  1. When an epic is moved to done, the automation is triggered
  2. All comments on the epic are pulled together and organized into a timeline
  3. AI reviews the comments, including sentiment, and drafts a retrospective
  4. The document is saved to Google Drive
  5. A link to the retro is placed back on the Jira epic
What you get

Retrospectives ready for a quick read-through

Every closed epic gets a written retrospective waiting in your Drive, with a link dropped right on the Jira ticket for your team to review.

What you get

A written retrospective document, saved and linked directly to the completed Jira epic.

What you need

A Jira account, a Google Drive account, and an OpenAI API key.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Manage email, calendar and tasks by chatting with an AI on Telegram

Send a text or voice message on Telegram and an AI assistant checks your calendar, email, and tasks for you.

Advanced

Automate new hire onboarding across Notion, Jira, and Slack

Sets up new employees automatically by generating welcome messages, IT tickets, and onboarding trackers.

Advanced

Scan every new Android app upload for risky code and alert Slack

Every new Android app file gets scanned for risky code automatically, with a plain-English summary sent straight to Slack.

Standard

Turn receipt photos into itemized Google Sheets rows

Drop a receipt into Google Drive and get every item, price, and tax broken out in a spreadsheet.

Advanced
Back to the AI Playbook