Jump to content

RefractTrack Attachments: Difference between revisions

From Pixel Refraction Studio
No edit summary
No edit summary
Line 1: Line 1:
== Attachments ==
== Attachments ==


Tasks can carry file attachments — a screenshot of a bug, a piece of reference art, a design doc, whatever's useful. By default, image files and zip archives are accepted; your admin can widen or narrow that list, and set a maximum file size, to suit your team.
Tasks can carry file attachments — a screenshot of a bug, a piece of reference art, a design doc, a sound cue, even a snippet of source code. RefractTrack accepts a wide range of file types right out of the box, grouped roughly like this:
 
* '''Images''' — jpg, png, gif, webp
* '''Archives''' — zip
* '''Office documents''' — pdf, Word, Excel, PowerPoint, and their OpenDocument equivalents, plus rtf
* '''Audio''' — wav, mp3, ogg, flac, and a handful of others
* '''Plain text and data''' — txt, markdown, csv, json, yaml, log files, and similar
* '''Source code''' — the usual suspects (C#, Java, Python, JavaScript/TypeScript, PHP, and more), plus a broad set of game-engine-specific scripting and scene formats (Godot, GameMaker, Ren'Py, Roblox Luau, Papyrus, and others), handy for attaching a snippet straight from your project
 
There's a small "?" button right next to the upload field on a task that lists everything currently accepted, grouped the same way, so nobody has to guess or come find this page mid-upload. An admin can widen or narrow the accepted list, and set a maximum file size, to suit your team — see your <code>config.php</code> if you're the one managing the server.
 
A couple of things are deliberately '''never''' accepted, on every install, for safety: anything that looks like an installer or executable, and <code>.svg</code> images (an SVG can secretly carry a script, which isn't something you want silently accepted as an "image").


=== Who can see what ===
=== Who can see what ===
Line 11: Line 22:
* [[RefractTrack_Tasks|Tasks]]
* [[RefractTrack_Tasks|Tasks]]
* [[RefractTrack_Permissions_and_Roles|Permissions and Roles]]
* [[RefractTrack_Permissions_and_Roles|Permissions and Roles]]
* [[RefractTrack_Export_and_Import|Export and Import]]


[[Category:RefractTrack]]
[[Category:RefractTrack]]

Revision as of 22:51, 11 September 2026

Attachments

Tasks can carry file attachments — a screenshot of a bug, a piece of reference art, a design doc, a sound cue, even a snippet of source code. RefractTrack accepts a wide range of file types right out of the box, grouped roughly like this:

  • Images — jpg, png, gif, webp
  • Archives — zip
  • Office documents — pdf, Word, Excel, PowerPoint, and their OpenDocument equivalents, plus rtf
  • Audio — wav, mp3, ogg, flac, and a handful of others
  • Plain text and data — txt, markdown, csv, json, yaml, log files, and similar
  • Source code — the usual suspects (C#, Java, Python, JavaScript/TypeScript, PHP, and more), plus a broad set of game-engine-specific scripting and scene formats (Godot, GameMaker, Ren'Py, Roblox Luau, Papyrus, and others), handy for attaching a snippet straight from your project

There's a small "?" button right next to the upload field on a task that lists everything currently accepted, grouped the same way, so nobody has to guess or come find this page mid-upload. An admin can widen or narrow the accepted list, and set a maximum file size, to suit your team — see your config.php if you're the one managing the server.

A couple of things are deliberately never accepted, on every install, for safety: anything that looks like an installer or executable, and .svg images (an SVG can secretly carry a script, which isn't something you want silently accepted as an "image").

Who can see what

Attachments follow the same access rules as everything else in RefractTrack: only people with permission to view attachments — and access to that specific project — can open a file. There's no way to guess or share a direct link that bypasses those checks; every download is checked first.