Project Files & Resources — Centralized View of All Project Attachments

Related existing discussions

Before posting this request, I searched the Vikunja Community and existing development issues for similar functionality.

I found the existing Attachments Management discussion, which is related to browsing uploaded attachments, and the Attachments as URLs discussion, which overlaps with the optional resources/URL portion of this proposal.

This request is specifically focused on a project-level centralized view that automatically aggregates attachments from all tasks belonging to that project while preserving the association with the original task.

Feature Request

Add a Files & Resources section to each project that provides a central place to find and access all files and resources associated with that project.

The Problem

Currently, files are attached to individual tasks. As a project grows, important files can become difficult to find because users need to remember which task contains the attachment.

For example, if a team member uploads a PDF to a task, another team member may know that the file belongs to the project but not know which task it was attached to.

Proposed Solution

Add a Files & Resources section at the project level that automatically collects and displays files associated with tasks in that project.

A file could still be uploaded directly to a task, preserving the context of why and where it was shared. However, it would also automatically appear in the project’s Files & Resources section.

This would provide two ways to access the same file:

  • From the task: See the file in its original context.
  • From the project: Find the file without needing to know which task contains it.

The project-level view should ideally show useful context such as:

  • File name
  • File type
  • Date uploaded
  • Uploaded by
  • Associated task
  • File size

Selecting the associated task could take the user directly to the task where the file was originally attached.

Resources

The same section could optionally support resources in addition to uploaded files—for example:

  • Web links
  • Google Docs/Sheets
  • SharePoint or Nextcloud links
  • Reference documents
  • Other URLs or project resources

This would make Files & Resources a central reference point for the project without requiring Vikunja to duplicate files that are already stored elsewhere.

Example

A project contains 75 tasks and 20 files scattered among those tasks.

Instead of searching through individual tasks to find a particular attachment, a user could open:

Project → Files & Resources

and immediately see all 20 files, including which task each file came from.

Key Principle

This should ideally be an aggregated project-level view rather than a separate attachment system.

A file attached to a task should remain associated with that task while also being discoverable from the project’s central Files & Resources section.

This would make project files significantly easier to discover while preserving the task-level context that Vikunja already provides.