# Create and edit 30+ diagram types on a Jira issue

Mermaid, draw.io, Excalidraw, PlantUML, BPMN, DMN, D2, Graphviz, DBML, Structurizr, Vega and more, from one editor with a searchable library picker, quick-access strip and per-language starter templates.

---

## Where you do it

![The diagram editor with the Templates dropdown open, listing Mermaid starters including User Journey, State Diagram, Flowchart, Sequence Diagram, Class Diagram, Entity Relationship Diagram and Gantt D](https://help.gocapable.com/images/d5f9eb06-46cf-4d97-b3be-f1e47309f2bb.webp)

Each library carries its own starter templates, so a new Mermaid diagram can begin as a user journey, a flowchart or a Gantt chart.

| **Task**                                              | **Where**                                                                              |
| ----------------------------------------------------- | -------------------------------------------------------------------------------------- |
| Install Diagrams for Jira and approve its permissions | Atlassian Marketplace → Jira → Apps → Manage apps                                      |
| Add a diagram to a Jira issue                         | Issue view → Diagram panel (or the Diagrams section in the issue details column) → Add |
| View a diagram full screen                            | Issue → Diagram panel → select a tab → View                                            |

---

## Settings that affect this

| **Setting**                              | **Where** | **What it does** |
| ---------------------------------------- | --------- | ---------------- |
| Admin / project / site settings          | \-        | \-               |
| Diagram (gadget configuration). Diagram  | \-        | \-               |
| Diagram (gadget configuration). Language | \-        | \-               |

---

## Worth knowing

* Diagrams for Jira is a separate purchase from the Confluence diagrams app and is not part of the Capable Suite.
* Editing a diagram is not a versioned update. The old attachment is deleted and a new one uploaded. The attachment id, author and created date change every time, and a failed upload after the delete loses the original silently.
* Diagram source for text-based languages leaves the Atlassian tenant and is sent to Capable's hosted rendering service. Draw.io, Excalidraw, BPMN and DMN never make that call. Nothing in the Jira edition lets an admin turn this off.
* The JQL field names carry an environment-specific 6-character prefix (the committed dev build shows ymwnmi\_diagram\_count, ymwnmi\_diagram\_updated, ymwnmi\_diagram\_types). Never publish a literal prefix as if it were universal. Tell readers to use the JQL field autocomplete.
* The global Diagrams page depends entirely on a search index that is only written on attachment add/delete events while the site is licensed. Pre-existing diagrams and diagrams changed during an unlicensed period never appear until the issue is touched again.
* Three requested scopes (manage:jira-webhook, manage:jira-configuration, manage:jira-project) plus storage:app have no matching code in the released Jira diagram capability. Admins reviewing the install prompt will see broader permissions than the app exercises.

---

## Limits that apply here

* Diagram title length
* Concurrent diagram previews on the browse page
* Diagram library catalogue

---

## Related

[Diagrams stored as ordinary Jira attachmentsAnother part of how this works.](https://help.gocapable.com/jira-diagrams/diagrams-stored-as-ordinary-jira-attachments.html)

[Site-wide diagram browserAnother part of how this works.](https://help.gocapable.com/jira-diagrams/site-wide-diagram-browser.html)

[How it worksThe rest.](https://help.gocapable.com/jira-diagrams/how-it-works.html)

---

_How it actually behaves._