File attachement management option
Nobody has claimed this yet.
- 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.
It is difficult to manage attachement file
Describe the solution you'd like
An administrative option to force the user to store the file in an appropriate folder instead of storing all at the same place.
Describe alternatives you've considered
I'd like an administrative option to forbid uploading new files but only attach already stored files
An option that delete automatically uploaded file, stored in the Deck folder when a card is deleted or when the board is deleted.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points; begin by locating Deck's attachment upload, storage, and deletion flows. Clarify the administrative settings and lifecycle rules for folder placement, upload restrictions, and cleanup, then define tests for each behavior before implementation.
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
- Needs clarification
- Newbie friendliness
- 20/100