Hello Atlassian Support,
In the past 1–2 weeks we have noticed a change in how Jira Cloud handles image attachments when printing or exporting issues. This is seriously impacting our workflows because we often need to generate PDF/Word reports including attachments.
Problem description:
When an image is inserted as an expanded attachment inside the issue, it appears extremely large when printing (takes up almost an entire page or multiple pages).
When exporting the issue to Word, the image does not render properly: either it becomes a huge blank space or the image fails to load (broken link).
When inserting the image as a link/thumbnail instead of expanded, the image does not appear at all in the print/export — only the link text is visible.
Adjusting the print scale (e.g. 70% or 30%) only affects the text, not the image size. The image always renders at full resolution.
This behavior was not present until recently (roughly 1–2 weeks ago).
Tests already performed:
Tried printing/exporting on Google Chrome → issue persists.
Tried printing/exporting on Microsoft Edge (v140) → issue persists (also noticed the incident reported in Atlassian Status Page regarding Edge + Strict Tracking Prevention, but in our case the issue also happens in Chrome, so it seems unrelated).
Tried with different scaling settings (70%, 30%, etc.) → no effect on image size.
Tried exporting to Word → image appears oversized or fails to render at all.
Tried attaching the same image as link/thumbnail → prints only as link text, not the image.
Tested in Chrome Incognito Mode → issue persists.
No option available to export to PDF natively in our Jira Cloud instance, only Word.
Expected behavior:
Attached images should be displayed consistently when printing/exporting issues.
Ideally, images should be resized to fit within the page (like they used to before).
Impact:
We cannot reliably generate printed reports or exports with attachments for clients.
Currently forced to manually resize attachments before uploading, or take screenshots as a workaround.
Could you please confirm if this is:
A known bug affecting Jira Cloud (beyond the Edge incident already reported)?
A recent change in how Jira handles attachments during print/export?
If there is a workaround or planned fix?
Thank you for your support!
