EpicStory Documentation
Setup, generation, publishing, credits, permissions, and admin guidance for EpicStory 7.
Version 7 uses Atlassian-hosted Forge LLM to produce editable AI drafts. AI generation is disabled during the Marketplace trial and requires an active paid license.
Quick start
Install, generate stories, and publish to Jira
Credits and models
How credit usage works in this release
Admin settings
Tenant and user credit policy controls
Security and privacy
Policy links and support channels
What EpicStory does
EpicStory turns Epic descriptions and Project requirements into structured Jira backlog drafts. The app generates stories and subtasks, lets teams review and edit details in Jira, and publishes only selected items when ready. Project users can also fully regenerate an active draft with a new instruction.
Quick start
- Install and activate a paid EpicStory license for your Jira Cloud site.
- Open a project epic and launch the EpicStory panel.
- Click Generate Stories. EpicStory currently shows Claude Haiku 4.5.
- Review AI-generated drafts, labels, subtasks, and acceptance criteria before relying on them.
- Use Publish to Epic to create the selected Jira issues.
Credits and models
EpicStory uses internal AI credits as usage guardrails. These credits are not stored value, a payment instrument, or Atlassian Marketplace currency. The UI expresses one internal USD budget unit as 1,000 AI credits.
- Generation currently uses Claude Haiku 4.5 through Forge LLM.
- Input and output token usage contributes to internal credit consumption.
- Admins manage shared tenant thresholds and per-user soft and hard guardrails.
- AI generation is disabled during the Marketplace trial.
Admin settings
Jira admins can configure installation-level settings from Jira administration:
- Credit Policy: tune soft cap, hard cap, warning threshold, and low balance thresholds.
- Licensed users: refresh the Jira Software licensed-user count used when calculating a future monthly tenant pool. Saving a policy does not replenish the current monthly balance.
Permissions
- Read Jira work: read Epic and Project context used for generation.
- Write Jira work: publish approved stories and subtasks.
- Read application roles: let an admin refresh the licensed Jira Software user count.
- Forge app storage: store operational jobs, credit ledgers, usage records, and application state.
Security and privacy
Start with the Privacy Policy, which currently serves as the main trust and legal entry point for EpicStory. Then review the supporting documents below before production rollout:
EpicStory produces AI-generated drafts. Teams should review generated output before publishing it or relying on it for delivery, security, or compliance decisions.
Production AI processing remains within Atlassian's Forge and Forge LLM platform. Forge-hosted persistent storage supports Atlassian residency controls, while transient compute and model routing may occur elsewhere for platform reliability. Review the AI Data Policy, Privacy Policy, and DPA for the applicable boundaries.
Support
Need help with setup, rollout, or troubleshooting? Reach out and include your Jira site, project key, and a short problem summary.