Abuse Reports: Update statuses #116
No reviewers
Labels
No Label
Priority
Critical
Priority
High
Priority
Low
Priority
Normal
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Type
Breaking
Type
Documentation
Type
Enhancement
Type
Feature
Type
Report
Type
Security
Type
Suggestion
Type
Testing
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: infrastructure/extensions-website#116
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "tmp-abuse-report-statuses"
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?
The previous status choices were:
There was no way to mark a report as "resolved". Besides, marking
something as "suspicious" doesn't sound too nice for the reporter.
Rename the statuses to the following:
@Oleg-Komarov +1?
as a side-note, i think we should split the components/status.html into a few separate model-specific components: now it is mixing status display logic for multiple models, and it is hard to be sure that we don't affect other models by accident