File attachments
Attachments keep the files needed to understand or complete work alongside the relevant item, so context does not live in a separate thread or drive.
Attach a file
Open the task, epic, or comment where the file belongs.
Use the attachment control in the editor or the item's detail view and choose your file.
The upload keeps the original filename, file size, and file type.
You can attach any file type; size limits apply. Typical uses include a brief, a design export, an error log, or supporting data.
Add a file to a specific comment when it supports that discussion. Add it directly to the task or epic when it is ongoing reference material for the work.
View and download attachments
Open the work item.
Choose the attachment you need. Images render as inline previews, so you can review visual context without leaving the item.
Download the file when you need a local copy.
Keep the item organized
Use descriptive filenames before uploading, especially for versions or exports.
Remove outdated attachments when they no longer help.
Add new context as a fresh attachment rather than replacing a file silently.
Attachment changes are included in the activity history, so the team can see when files were added or removed and find the current context. See Comments & activity timeline.
Use links for work dependencies
An attachment explains the work; a task link explains how work items depend on one another. If a file reveals that a task cannot proceed, add the relevant blocking link as well so the dependency is visible in planning views. See Task links & dependencies.
Related
Was this article helpful?