Let Map Admin Remove Submissions #270
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: StrafesNET/maps-service#270
Reference in New Issue
Block a user
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?
There are lots of mapfixes being submitted via submissions rather than via the maps page. Currently there is no way to clean these up, which makes sifting through submissions a pain (on top of no filter currently, but that is coming later). Another lesser use case would be removing duplicate submissions / mapfixes when they use a different model, instead of just rejecting it and having it add to the pile.
Personally I was imagining map council / admin utilizing filters to display mapfixes / submissions with Submitted status to check which maps are submitted to cut away the clutter. We don't have filters on the browsing pages yet. Requiring users to submit just to be able to reject the submission and clear their submission slot is not a clear process, but I don't think map council force-deleting submissions is any better.
Filters would make it a lot easier for currently submitted maps, but for people who want to revisit rejected maps the issue still stands. There is no reason to keep a mapfix in the submissions list, so I believe it should be removed. Maybe an option to mark a submission as wrong or misallocated to separate it from just rejected would be better if you don't like it being removed.
What does this mean?
Not more statuses and buttons 😭
If you left for a while or missed aor and wanted to see why your submission was rejected, or you just want to look at the rejected maps of old aors for whatever reason. You still have to sift through a bunch of rejected mapfixes because theyre in the wrong area.
A dedicated filter for your personal submissions is the intended way to find out if your submission was accepted. Filtering would make a lot of things better...
I think this is a good proposal. The duplicate submissions and accidental submissions can be cleaned up. Rejected maps should not be deleted though.
Sounds like most of this was resolved by the new dashboards. The last use case about AOR rejections would likely be solved when !271 gets implemented. Recommend not moving forward with a delete button.