Documentation

Overview

Recap turns the work you have already completed in Jira into a written monthly status report. You open one screen, click a button, and Recap produces a few short paragraphs — grouped by epic — that you can paste into a status update, a 1:1 document, or a performance review. It is built entirely on Atlassian Forge, stores nothing, and sends no data to third parties.

Requirements

• A Jira Cloud site (Recap does not support Server or Data Center).
• Jira issues assigned to you that have reached a Done status in the last 30 days — this is the work Recap reports on.
• An active Recap subscription (a free trial is available from the Marketplace). See Licensing & billing.

Installation

Recap is installed by a Jira site administrator from the Atlassian Marketplace:

1. On the Recap Marketplace listing, click Try it free (or Get it now).
2. Choose the Jira site to install onto and confirm. Recap requests a single read-only permission, read:jira-work.
3. Once installed, Recap appears for all users under Apps in the Jira top navigation.

Generating a report

1. In Jira, open Apps in the top navigation and select Recap.
2. Click Generate my report. Recap gathers your completed work and writes it up — this usually takes a few seconds.
3. Read the report in the text box. Edit it if you like, then select all and copy (see Copying your report).
4. Need a fresh version? Click Regenerate at any time.

How the report is built

Recap follows the same steps every time you click Generate:

1. It finds your recently completed work

Recap looks for issues assigned to you that moved into a Done status category within the last 30 days. The 30-day window is fixed. Conceptually, the query is:

assignee = currentUser()
AND statusCategory = Done
AND statuscategorychangedate >= -30d

Recap reads only the fields it needs — issue key, summary, parent (epic), project, and completion date — and it pages through every matching issue, so a busy month with hundreds of completed issues is handled correctly.

2. It groups the work by epic

Each issue is grouped under its epic (the issue's parent). Issues that are not part of an epic fall back to being grouped under their project, so nothing is left out. Groups are ordered with the largest first, and within a group the most recently completed work comes first.

3. It writes the report

The grouped work is turned into plain, past-tense prose using Atlassian's built-in AI (Forge LLMs). The writing is deliberately factual: it summarises what the issue titles say and nothing more. Recap does not invent metrics, dates, or achievements that are not present in your Jira data.

Screen states explained

Depending on your data and licensing, Recap shows one of the following:

Copying your report

The report appears in an editable text box. To copy it: click inside the box, press Ctrl/Cmd + A to select everything, then Ctrl/Cmd + C to copy. You can edit the text first — tweak wording, remove a line, or add context — before copying it wherever your updates live.

Data & permissions

• One permission. Recap requests only read:jira-work (read-only) and acts as you, so it can never surface an issue you could not already see.
• No storage. Recap has no database and uses no Forge storage. Reports are generated in memory and returned to your browser; nothing is kept.
• No third parties. Everything runs on Atlassian Forge, and report text is written using Atlassian-hosted AI. No data leaves the Atlassian platform.

Full detail is in the privacy policy.

Licensing & billing

Recap is a paid app, licensed and billed through Atlassian (it appears on your regular Atlassian bill). A free trial is available from the Marketplace so you can evaluate it before subscribing. Pricing is per user per month, with volume discounts at higher tiers.

If an installation is not licensed, Recap shows “A subscription is required” instead of generating a report. Licensing is managed by your Jira site administrator from Manage apps in Jira administration.

Troubleshooting

My report is empty, but I did complete work.

Check that the issues were assigned to you and that they reached a Done status (not just “In Review” or a custom status that is not mapped to the Done category) within the last 30 days.

Work is grouped under a project name, not an epic.

That is expected for issues that are not linked to an epic. Set an issue's parent to an epic if you want it grouped under that epic instead.

I keep getting the “Basic report” notice.

This means the AI writer was temporarily unavailable and Recap used its built-in fallback so you were not left empty-handed. Wait a moment and click Regenerate. If it persists for an extended period, contact support.

It says a subscription is required.

The app is not licensed on this site. Ask your Jira administrator to start a trial or subscribe from the Atlassian Marketplace.

Version history

Support

Questions, problems, or feedback? Email support@isogunlabs.com. Best-effort support; typical response time is 1–2 business days.