Site-wide diagram browser
An Apps-menu page listing every issue that has diagrams, with project and type filters, List and Grid views, thumbnails and paging.
#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 | - | - |
#Worth knowing
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.
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
How it actually behaves.
