← All issues

Allow adding images to issues

Completed
Posted by Kristaps4 votesImprovementFeedback

We need to be able to upload images here, to help illustrate any bugs or issues.

Ideally inline in the text area (Description).

I don't see a way to do that right now.

Comments (2)

Sign in to post a comment.

  • Daniel Brooks

    Strong agree from the support world. A screenshot is worth a dozen back-and-forth messages: error dialogs, settings screens, and what the visitor actually sees are hard to describe in words, and half the time the written description leaves you guessing which screen someone is even on. Inline images in the description would help, and the same goes for comments, since follow-up screenshots are often where the real clue shows up. This would make reports here much easier to act on.

  • Daniel Brooks

    Adding to my comment above — I've been thinking about what would make this actually work in practice, because getting an image into a report is only half of it. The other half is keeping those images useful and safe.

    First, paste-from-clipboard support matters more than a file picker. In a real support flow the screenshot is already on your clipboard nine times out of ten, and forcing someone to save a file and then browse for it breaks the momentum completely. Drag-and-drop into the description box is the next best thing.

    Second, some light annotation would go a long way: arrows, boxes, and especially blur. Half the screenshots I see would benefit from a box drawn around the actual problem area, and blur is almost a requirement — people paste shots with customer names, email addresses, and API keys visible without realizing it. If the portal is going to host these images, a one-click redact before posting protects everyone.

    Third, think about mobile. A lot of visitors file feedback from their phones, and uploading a full-resolution photo of their screen over a slow connection just fails silently. Client-side compression with a sensible size cap, plus a thumbnail preview before submit, would prevent a lot of frustration.

    Finally, inline placement in the description — not attachments dumped at the bottom — is what makes a report scannable. When the screenshot sits right next to the sentence describing it, whoever triages doesn't have to scroll up and down matching image 3 to paragraph 2. That is the difference between a report that gets acted on and one that sits in the queue. This looks small on a roadmap and ends up saving hours every week once it ships..