Very large diagrams do not render at all
What you are seeing
Very large diagrams do not render at all.
#Why it happens
Diagram source under 4,300 encoded characters is rendered through a GET URL; larger source is posted instead. Source too large to encode at all is dropped with only a console warning.
#What to do
Split a very large diagram into smaller ones, or use a browser-rendered type (draw.io, Excalidraw, BPMN, DMN) which does not go through the rendering service at all.
#Settings involved
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
Diagrams page under Apps is empty, or is missing diagrams that definitely exist on issues
The browse page finds diagrams through a search index that is only written when a diagram
Diagrams page is empty and every surface shows a "License Not Found" or "License expired" banner
Licensing is enforced in production. With no licence the app is replaced by the banner, an
Something is missing or looks wrong
The rest of this family.
Found it? Good.
