Installation
StoryPulse is installed directly from the Atlassian Marketplace — no separate account or external setup is required. It works on Jira Cloud only.
-
1
Find StoryPulse on the Marketplace
Go to your Jira instance → Apps → Find new apps → search for StoryPulse.
-
2
Install with one click
Click Try it free. The app installs instantly — no restart, no configuration required.
-
3
Open StoryPulse
Go to Apps → StoryPulse in the Jira navigation. The app opens in a full-page view.
No admin setup needed. StoryPulse reads your existing Jira data using your own permissions. There is nothing to configure before generating your first report.
Your first report
Generating a report takes four steps. The whole process takes under two minutes.
-
1
Select your project and sprint
Search for any Jira project by name. Then pick the sprint you want to report on — or select multiple sprints for a combined narrative.
-
2
Choose a report template
Pick from Sprint Story, Stakeholder Update, Retrospective Narrative, or Delivery Summary. Each template structures the report differently for its intended purpose.
-
3
Select your audience
Choose who the report is for — Engineering Team, VP/Leadership, External Stakeholder, or Board/Investor. StoryPulse adjusts the tone, depth, and terminology automatically.
-
4
Generate and publish
Click Generate Report. Review the narrative, optionally refine it with follow-up instructions, then publish directly to Confluence or export in another format.
Required permissions
StoryPulse is built on Atlassian Forge. It uses your own Jira and Confluence permissions — it can only access projects and spaces you already have access to. No additional permissions are granted by installing the app.
To generate reports, you need read access to the Jira project and sprint data. To publish to Confluence, you need create page permission on the target Confluence space.
Report templates
StoryPulse includes four report templates. Each one structures the narrative differently, emphasising the data that matters most for its purpose.
Sprint Story
Velocity, completed vs. planned issues, epic progress, carry-forward work. The standard end-of-sprint narrative for engineering teams.
Stakeholder Update
Plain English outcomes for non-technical readers. No sprint terminology. Focused on what was delivered and what it means for the product.
Retrospective Narrative
A balanced, honest team-facing story of what worked, what didn't, and what was completed. Designed for retro sessions.
Delivery Summary
Planned vs. actual delivery with gap analysis and roadmap impact. Ideal for release reviews and milestone reporting.
Free plan: Includes the Stakeholder Update template. All four templates are available on Standard and above.
Audience modes
Every template can be written for four different audiences. Selecting an audience changes the tone, depth, vocabulary, and which details are emphasised — the underlying data is the same.
Engineering Team
Technical detail, issue references, sprint metrics, and team-level observations. Written by developers, for developers.
VP / Leadership
Outcome-focused, concise. Highlights risks, blockers, and delivery confidence. No sprint jargon.
External Stakeholder
Written in plain business English. No Jira terminology. Suitable for clients, partners, or non-technical product stakeholders.
Board / Investor
High-level narrative focused on strategic progress, milestones, and business impact. Concise and formal in tone.
Sprint mode
Sprint mode is the default. Select a Jira project and one or more sprints (up to five) to include in a single report. Multi-sprint reports combine the data into a single narrative covering the full period.
Sprint mode works with any Scrum project that has active or completed sprints in Jira.
Date range mode
Date range mode lets you report on any custom time period — regardless of sprint boundaries. It is useful for monthly or quarterly updates, and it is the right mode for Kanban projects that don't use sprints.
Select your project, pick a start and end date, and StoryPulse fetches all issues updated in that period.
Standard plan and above. Date range mode is not available on the Free plan.
Publishing to Confluence
After generating a report, click Publish to Confluence. You will be asked to:
- Select the Confluence space to publish to
- Choose a parent page (optional — leave blank to publish at the top level of the space)
- Confirm or edit the page title
StoryPulse creates a fully formatted Confluence page with panels, headers, and the AI-generated narrative. If a page with the same title already exists in that space, you will be asked to confirm before overwriting it.
Tip: You need Create Page permission on the target Confluence space. If you don't see a space in the dropdown, ask your Confluence admin to grant you access.
AI refinement
After generating a report, you can refine it with plain English follow-up instructions. Type your instruction in the Refine panel and the report updates in place.
Examples of refinement instructions:
- "Make it shorter"
- "Use a more formal tone"
- "Focus on the payments epic"
- "Add more detail about the blockers"
- "Rewrite the opening paragraph"
Refinement rounds are counted toward your monthly usage. The number of refinements available depends on your plan.
Export formats
In addition to publishing to Confluence, you can export any report as:
- Email paragraph — ready to paste into an email or calendar invite
- Slack message — formatted for Slack, with appropriate length and tone
- Bullet points — a clean summary list for presentations or notes
- Meeting talking points — structured prompts for a standup or review meeting
- LinkedIn post — a public-facing highlight of the sprint's achievements
- PDF — a formatted document for external sharing
Standard plan and above. Export formats are not available on the Free plan.
Plan comparison
| Feature | Free | Standard | Premium |
|---|---|---|---|
| Reports per month | 5 | 30 | Unlimited |
| Users | Up to 10 | Up to 50 | Unlimited |
| Sprint mode | ✓ | ✓ | ✓ |
| Confluence publishing | ✓ | ✓ | ✓ |
| AI refinement | ✓ | ✓ | ✓ |
| Stakeholder template | ✓ | ✓ | ✓ |
| All 4 report templates | — | ✓ | ✓ |
| All 4 audience modes | — | ✓ | ✓ |
| Date range mode | — | ✓ | ✓ |
| Export formats | — | ✓ | ✓ |
| Project context memory | — | ✓ | ✓ |
| Multi-sprint (up to 5) | — | ✓ | ✓ |
| Price | Free | $2.50/user/mo | $5.00/user/mo |
Billed through the Atlassian Marketplace. No separate account needed.
Usage & limits
Report usage is counted per calendar month and resets on the first of each month. The usage counter is shared across all users in your Jira instance — it is not per-user.
You can see your current usage and remaining reports in the StoryPulse app. When you reach your monthly limit, generating new reports is paused until the counter resets or you upgrade your plan.
Refinement rounds (using the AI refine panel after generation) are counted as separate report uses.
Frequently asked questions
Does StoryPulse store my Jira data?
No. Issue data is fetched at the time of report generation and used only to produce the report you requested. It is not stored, logged, or retained by StoryPulse after the request completes.
Which Jira project types are supported?
StoryPulse works with Scrum projects (sprint mode) and Kanban projects (date range mode). It requires Jira Cloud — it is not available for Jira Data Center or Jira Server.
Can I publish a report to any Confluence space?
Yes — any Confluence space in the same Atlassian instance that you have Create Page permission on. StoryPulse cannot publish to Confluence instances outside your current Jira site.
What happens if I overwrite an existing Confluence page?
StoryPulse detects if a page with the same title already exists in the target space and asks you to confirm before overwriting. The previous version of the page is preserved in the Confluence page history.
Can multiple team members use StoryPulse?
Yes. Any user in the Jira instance who has the app installed can use StoryPulse within the plan's user and report limits.
What AI model powers StoryPulse?
StoryPulse uses Claude by Anthropic to generate report narratives. Your Jira data is sent to Anthropic's API for processing and is governed by Anthropic's usage policies. It is not used to train AI models.
How do I cancel or change my plan?
Plans are managed through the Atlassian Marketplace. Go to your Jira instance → Apps → Manage apps → StoryPulse to change or cancel your subscription.
Something isn't working — how do I get help?
Visit our support page to contact the team. We aim to respond within one business day.
Ready to generate your first report?
Install StoryPulse free from the Atlassian Marketplace. No setup required.
Get StoryPulse Free →