nextcloud / nextcloud/deck

Separate the uploaded files in their own board/card directory in the /Deck folder

Open
#6,357 0 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: attachments
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
When I uploaded files in a list, and in another list I uploaded the exact same file, but that got rename with (2) in the file name.

Describe the solution you'd like

It would be wiser to separate the uploaded files in their own board folder in the /Deck directory.

Examples:

  • /Deck/ProjectName/FileUploaded.txt
  • /Deck/board/FileUploaded.txt
  • /Deck/Personal/Report.pdf
  • /Deck/Personal/Backlog/The Full report.pdf

Or use the IDs from the url, as the folder names:

  • /Deck/board/18/card/264/report.pdf

Or just the IDs numbers without the naming

  • /Deck/18/264/report.pdf

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how Deck uploads files into the /Deck directory and how duplicate filenames are currently handled. Compare the proposed board- and card-based folder layouts, then define which layout should be used; done means uploads from different lists or cards no longer collide and the chosen paths are consistent.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.