Skip to main content
An issue can carry the screenshots, logs and documents that explain it, and link the drawings that sketch it. Files belong to the issue, and everyone who can read the issue can open them.
Attachments need file storage set up on your ReasonOS deployment. Until it is, adding a file is refused with “The issue attachment store is not configured on this workspace.” Ask whoever runs your deployment to enable it.

​
Add a file

There are three ways to add a file to an issue you can edit:
  • Paste a screenshot or file into the description or a comment while you write.
  • Drop files onto the description or a comment.
  • Choose Add attachment on the issue’s Attachments card and pick files.
Each file shows its progress while it uploads, and you can keep typing. A screenshot or other image appears in the text where you pasted or dropped it. Any other file becomes a link at that spot. Files added to a comment you are writing are attached when you post it. If posting fails, your words and the uploaded files stay, so you can post again.
A new issue takes no files until it exists. Create it first, then paste or drop files into its description or a comment.

​
What opens where

  • Images (PNG, JPEG, GIF and WebP) show inline in the issue and open in the browser.
  • Every other file downloads when you open it, including SVG images and PDFs. Nothing a file contains runs in ReasonOS.
The Attachments card lists the files on the issue itself, with their size, who added them and when. Files added to a comment appear under that comment. Choose Link a drawing on the Attachments card to pick from the organization’s drawings you can open. The drawing appears on the card and opens in Drawings. A reader who can’t open that drawing sees A drawing you cannot open in its place. They don’t see its name, and the link doesn’t open it. The same happens when a linked drawing has been deleted. Choose the remove button on a row, then confirm. Removing a file also removes it wherever the description or a comment shows it, and those places show a missing file instead. ReasonOS doesn’t rewrite anyone’s words to hide that. Removing a drawing link leaves the drawing itself unchanged.

​
Who can see and add files

  • Members who can edit the project’s issues can add and remove files and drawing links.
  • Readers of a public project, signed in or not, can view and download its files. They can’t add or remove them.
  • People outside a private project can’t open its files at all, even with a direct link.

​
Limits

  • 25 MB per file. A larger file is refused with “This file is larger than the 25 MB attachment limit.”
  • Organization storage. Your plan sets how much attachment storage your organization has in total. When it is full, new uploads are refused with a sentence showing how much is used. Files already attached stay readable. Removing files frees their space.
If ReasonOS can’t confirm an upload finished, it says the attachment may have been saved. Refresh the issue before trying again, so the file isn’t added twice. The same goes for editing a comment: if ReasonOS can’t confirm the edit was saved, it says so, keeps any files you added, and asks you to refresh before editing again.

​
Agents and MCP

Agents and MCP clients read attachments with your permissions, through the same checks as the issue page. get_task lists an issue’s files and drawing links, and read_task_attachment returns a file’s contents. Files are added in the browser, not through MCP. See Work tools on managed branch servers.