Diagrams in Jira

Capable Diagrams for Jira puts the same editors on Jira issues: the same languages, the same canvas editors, the same storage model inside your own site.

It is a separate app, because Jira and Confluence are separate products, but the diagrams behave the same way.

#When this matters

Architecture or process diagrams that belong on a ticket rather than a page.
Incident tickets where a timeline or topology diagram is the fastest explanation.
Teams working primarily in Jira.

#The detail

Thing	What happens
Editors	The same set: draw.io, Excalidraw, BPMN, DMN and the text languages.
Storage	In your Jira site, under the issue's permissions.
Licensing	A separate app and a separate subscription.
Sharing	Diagrams are per product; a Jira diagram is not a Confluence diagram.

#A few things that catch people out

It is a separate app with its own licence. Installing one does not install the other.
A diagram on an issue follows the issue's permissions, the same way a page diagram follows the page.
Copying between products means exporting and importing, not referencing.

Capable Search

Finding pages by the diagrams on them.

Capable Markdown

Diagrams inside a fenced code block.

Examples

Working diagrams you can copy.

It works better next to the rest of Capable.