Documentation
EpicViz for Jira
What EpicViz does: EpicViz reads your Jira epic and its child issues, then uses AI to generate an architecture diagram — flowchart, C4 context, C4 container, or sequence — directly in the Jira issue panel. No copy-pasting, no manual drawing.
Installation
EpicViz is installed through the Atlassian Marketplace:
- Go to the Atlassian Marketplace and search for "EpicViz"
- Click Get it now and select your Jira site
- Accept the permissions prompt — EpicViz only requests
read:jira-work - The app is immediately available — no configuration required
EpicViz runs on Atlassian Forge and requires no server setup, API keys, or external accounts.
Finding the Panel
After installation, the EpicViz panel appears on every Jira issue. To use it effectively:
- Navigate to any Epic issue in Jira
- Scroll down to the issue panel section — look for the EpicViz tab
- The panel shows the epic's child issues and diagram controls
EpicViz works best with epics that have at least one child issue (story, task, or bug) linked to them. Epics with no child issues will show an empty state message.
Generating a Diagram
Generating a diagram takes under 10 seconds:
- Open an epic in Jira
- Find the EpicViz panel
- Select a diagram type from the dropdown
- Click Generate
- The diagram renders inline — pan and zoom to explore it
You can switch between diagram types and regenerate at any time. Each generation is fresh — EpicViz does not cache diagrams between sessions.
Exporting diagrams
Use the Export button to download the diagram as a PNG image for use in documentation, presentations, or wikis.
Flowchart
The flowchart diagram shows how work flows through the epic — tasks, decisions, and dependencies between child issues.
Best for: Understanding task sequencing, identifying blockers, and sharing a high-level process view with stakeholders.
Rendered using React Flow with automatic Dagre layout. Nodes represent individual issues; edges represent logical flow and dependencies inferred from issue summaries and types.
C4 Context Diagram
The C4 Context diagram shows your system in relation to external actors — users, external systems, and dependencies.
Best for: Communicating system boundaries to non-technical stakeholders, onboarding new team members, and documenting how your system fits into a larger ecosystem.
Based on the C4 model by Simon Brown. EpicViz infers actors and systems from the epic and child issue descriptions.
C4 Container Diagram
The C4 Container diagram breaks the system into its major containers — services, databases, frontends, and APIs — and shows how they interact.
Best for: Architecture reviews, sprint planning, and communicating internal system structure to engineers.
Sequence Diagram
The sequence diagram shows the order of interactions between system components or actors over time.
Best for: Documenting API flows, authentication sequences, and multi-step user interactions.
Rendered using Mermaid. The diagram shows participants and message flows inferred from child issue summaries.
Free vs Paid
| Feature | Free | Paid |
|---|---|---|
| All 4 diagram types | ✓ | ✓ |
| Flowchart, C4, Sequence rendering | ✓ | ✓ |
| PNG export | ✓ | ✓ |
| Child issue summaries used for AI context | ✓ | ✓ |
| Enhanced Ticket Understanding (child issue descriptions) | ✗ | ✓ |
Subscriptions are managed through the Atlassian Marketplace. There is no EpicViz account to create — billing is handled entirely by Atlassian.
Enhanced Ticket Understanding
On paid plans, EpicViz includes child issue descriptions (in addition to summaries) when generating diagrams. This gives Claude more context about what each issue actually does, resulting in:
- More accurate component names and relationships
- Better identification of external dependencies and actors
- Richer sequence flows that reflect actual implementation details
Up to 200 characters of each child issue description are included. Descriptions are passed to the Atlassian-hosted Claude model and are never stored by EpicViz.
FAQ
Does EpicViz work with company-managed (classic) Jira projects?
Yes. EpicViz uses a two-step fallback to find child issues — first via the parent field (team-managed projects), then via Epic Link (company-managed classic projects).
Does my Jira data leave Atlassian's infrastructure?
No. EpicViz runs entirely on Atlassian Forge. All processing — including the AI diagram generation — happens within Atlassian's own infrastructure. See the Privacy Policy for full details.
Why is my diagram empty or minimal?
This usually happens when the epic has no child issues, or child issue summaries are very short. Add more descriptive issue titles and try regenerating. Paid plans also include issue descriptions for richer output.
Can I regenerate a diagram?
Yes — click Generate again at any time. Each generation is independent and may produce a slightly different diagram as the AI interprets your issue data.
What Jira permissions does EpicViz require?
EpicViz requests only read:jira-work — read access to issues and epics. It does not request write access and cannot modify any Jira data.
Support
For questions, bug reports, or feature requests, contact us at:
We aim to respond within 2 business days.