Where diagrams are stored
Saving does POST /rest/api/3/issue/{key}/attachments with a file named <Title><extension>, using your own Jira permissions. The extension comes from the diagram language (mermaid → .mermaid, drawio → .drawio, excalidraw → .excalidraw, and so on). Diagrams therefore appear in the issue's Attachments field and travel with normal Jira attachment handling. Gadget diagrams are the exception. They live in the gadget's own configuration.
#What it does
As ordinary Jira issue attachments. Not in a Capable data store.
#Where you do it
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 | - | - |
#Limits that apply here
Limit | Value | What happens |
|---|---|---|
Diagram title length | - | The Title input is capped at 50 characters. Titles are used verbatim as attachment filenames with no de-duplication or sanitisation, so two diagrams with the same title produce two identically named a |
Browse page size | - | Each JQL page requests 12 issues and the list reveals 12 rows at a time; Show more loads the next batch. (The shared hook's own default is 50; the Diagrams page overrides it to 12.). |
Concurrent diagram previews on the browse pa | - | Diagram content is downloaded one attachment at a time through a throttle, so thumbnails on a busy site fill in progressively rather than all at once. |
#Related
Better with company.
