Admin view of all users' download jobs and files, including soft-deleted ones
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 24/100
Research direction
Start by reading the implementation of CurrentUserExtension, the soft-delete filter, and issue #47 to understand how download jobs and files are currently scoped and retained. The proposal also calls for admin API operations and PWA views, plus restore and permanent-delete actions that remove files from disk. Agree on the endpoint design and required admin role first; done means admins can distinguish, restore, and permanently delete soft-deleted records.
Written by the indexing model from the issue text.
Description
Follow-up of #47.
Context
#47 soft-deletes DownloadJobs (when their owner deletes them) and DownloadedFiles (when all jobs linked to them are soft-deleted). The data is kept in the database, intended to be visible to admins, but no admin view exists:
CurrentUserExtensionrestricts every API query on owner-filterable resources to the current user's own records, admins included.- The gedmo soft-delete filter hides deleted records for everyone.
Proposal
- Let
ROLE_ADMIN(orROLE_DOWNLOAD-API_ADMIN) bypass the owner restriction inCurrentUserExtension, or add dedicated admin operations. - Disable the soft-delete filter for admins on those operations, and expose
deletedAtso deleted records can be told apart. - Admin actions on soft-deleted
DownloadedFiles: restore, and permanently delete (including removing the file from disk, which #47 deliberately never does automatically). - Admin panel (PWA) views for the above.
Open questions
- Reuse the existing endpoints with a role-based bypass, or separate
/admin/...operations? - Which role should get access:
ROLE_ADMINor onlyROLE_DOWNLOAD-API_ADMIN?
- Dominant language
- PHP
- Stars
- 1
- Forks
- 0
- Avg merge
- 3d 50m
- Merged PRs (30d)
- 9
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from FetchDock/fetchdock-server
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
FetchDock/fetchdock-server#54 ·
Maintainers usually reply within 1 day
-
bug dependencies
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
FetchDock/fetchdock-server#53 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
FetchDock/fetchdock-server#23 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
FetchDock/fetchdock-server#22 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 38/100
FetchDock/fetchdock-server#21 ·
Maintainers usually reply within 1 day
All issues in FetchDock/fetchdock-server
Similar issues
-
AI effort: [XS] priority: medium severity: minor type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Exclude module `require-dev` and `autoload-dev` from the generated `composer.json`Possibly taken @keiserjb claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
uiowa/uiowa#10310 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mailcow/mailcow-dockerized#7677 · 1 comment ·
Maintainers usually reply within 1 day