Drop-OSS/drop
1
0
Fork 0
mirror of https://github.com/Drop-OSS/drop.git synced 2026-07-21 16:15:24 -04:00
Code Issues 77 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #260] FR: issues reporting from users #134

New Issue
Open
opened 2026-02-17 17:06:14 -05:00 by yindo · 2 comments
yindo commented 2026-02-17 17:06:14 -05:00
Owner
Copy Link
Copy Source

Originally created by @binarygeek119 on GitHub (Oct 8, 2025).
Original GitHub issue: https://github.com/Drop-OSS/drop/issues/260

Being able to flag things about store items.

Issue types
Virus alart
Bad install
Update request
Needs dependencies
Wrong metadata
Etc

Originally created by @binarygeek119 on GitHub (Oct 8, 2025). Original GitHub issue: https://github.com/Drop-OSS/drop/issues/260 Being able to flag things about store items. Issue types Virus alart Bad install Update request Needs dependencies Wrong metadata Etc
yindo added the featureconfirmed labels 2026-02-17 17:06:14 -05:00
yindo commented 2026-02-17 17:06:14 -05:00
Author
Owner
Copy Link
Copy Source

@Pacodastre commented on GitHub (Oct 23, 2025):

So the idea for this would be to have a report button on the store page. Clicking this button would open a modal window. The modal window would have a dropdown list containing the list of problems, and a text field for the user to explain what is wrong.
There would also be a dedicated section in the admin, for admin users to see reports in a table. The report will contain the category, the description entered by the user, the reporter name, and the date this was reported.

In the future it could also be expanded and integrate with other features.

@binarygeek119 does this align with what you had in mind? Do you have further suggestions?

@Pacodastre commented on GitHub (Oct 23, 2025): So the idea for this would be to have a report button on the store page. Clicking this button would open a modal window. The modal window would have a dropdown list containing the list of problems, and a text field for the user to explain what is wrong. There would also be a dedicated section in the admin, for admin users to see reports in a table. The report will contain the category, the description entered by the user, the reporter name, and the date this was reported. In the future it could also be expanded and integrate with other features. @binarygeek119 does this align with what you had in mind? Do you have further suggestions?
yindo commented 2026-02-17 17:06:14 -05:00
Author
Owner
Copy Link
Copy Source

@binarygeek119 commented on GitHub (Oct 24, 2025):

that all sounds great

@binarygeek119 commented on GitHub (Oct 24, 2025): that all sounds great
yindo changed title from FR: issues reporting from users to [GH-ISSUE #260] FR: issues reporting from users 2026-06-05 14:21:39 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
duplicate
feature
feature
good first issue
needs-triage
pull-request
Mirrored from GitHub Pull Request
 qol
support
No Label confirmed feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Drop-OSS/drop#134
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?