Difference between revisions of "Reports"
| Line 15: | Line 15: | ||
**Optional. This space can be used to describe/describe in further detail the nature of the report. Line breaks will be preserved, but HTML will not be rendered. | **Optional. This space can be used to describe/describe in further detail the nature of the report. Line breaks will be preserved, but HTML will not be rendered. | ||
| − | === Submission === | + | ===Submission=== |
| − | Reports submitted to the queue cannot be edited by the user. | + | Reports submitted to the queue cannot be edited by the user. The report will have its own page containing all submitted information. A report's visibility depends on its nature; content reports will not be visible to any users besides the submitter and users with the Manage Reports power. Bug reports, however, are listed publicly in the bug report index (to prevent duplicate reports). If an exploit has been reported, however, the report will be hidden until the report is closed (and the issue presumably addressed). |
| + | |||
| + | == Report Queue == | ||
| + | Users with the '''Manage Reports''' power can view the queue, assign themselves to reports, respond as appropriate, and close reports. | ||
| + | |||
| + | The report queue consists of lists of submissions filtered by status, ordered by newest first. Pending reports can be acted upon, while closed reports are for reference only. | ||
| + | |||
| + | Clicking the edit button takes the user to the report review page, where they can assign, comment on, or close the report depending on its status. | ||
* | * | ||
[[Category:Documentation]] | [[Category:Documentation]] | ||
Revision as of 09:39, 16 July 2021
Reports are a submission type added in 2.0.0 that accepts user content and bug reports into a queue. They can be viewed and processed in the admin area by users with the Manage Reports power.
Submission
Reports can be submitted from the report submission page. A link to this is also available on the bug report index for logged-in users, and "report content" buttons are present on pages with user-submitted content.
A report requires:
- URL/Title
- Either a link to offending content (content report) or a short summary of the bug (bug report)
- Is/Is Not Bug Report (Toggle)
- Whether or not the report is for a bug. If this is on, an additional field for specifying the type of bug appears.
- Error Type (if bug report)
- The type of error being reported. By default, the options are: 500 error, 404 error, text error, exploit, or other error.
- Comments
- Optional. This space can be used to describe/describe in further detail the nature of the report. Line breaks will be preserved, but HTML will not be rendered.
Submission
Reports submitted to the queue cannot be edited by the user. The report will have its own page containing all submitted information. A report's visibility depends on its nature; content reports will not be visible to any users besides the submitter and users with the Manage Reports power. Bug reports, however, are listed publicly in the bug report index (to prevent duplicate reports). If an exploit has been reported, however, the report will be hidden until the report is closed (and the issue presumably addressed).
Report Queue
Users with the Manage Reports power can view the queue, assign themselves to reports, respond as appropriate, and close reports.
The report queue consists of lists of submissions filtered by status, ordered by newest first. Pending reports can be acted upon, while closed reports are for reference only.
Clicking the edit button takes the user to the report review page, where they can assign, comment on, or close the report depending on its status.
