Reports - Revision history

Mercury at 17:08, 16 July 2021

2021-07-16T17:08:56Z

Mercury at 17:01, 16 July 2021

2021-07-16T17:01:53Z

Mercury at 16:39, 16 July 2021

2021-07-16T16:39:30Z

Mercury at 16:33, 16 July 2021

2021-07-16T16:33:03Z

Mercury at 16:30, 16 July 2021

2021-07-16T16:30:32Z

Mercury at 16:29, 16 July 2021

2021-07-16T16:29:35Z

Mercury: Protected "Reports": High traffic page ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2021-07-16T16:24:33Z

Protected "Reports": High traffic page ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

Mercury: Created page with "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..."

2021-07-16T16:24:26Z

Created page with "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..."

New page

Reports are a submission type added in [[Updating: to 2.0.0|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.
[[Category:Documentation]]

@@ Line 1: / Line 1: @@
-Reports are a submission type added in [[Updating: to 2.0.0|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.
+Reports are a submission type added in [[Updating: to 2.0.0|2.0.0]] that accepts user content and bug reports into a queue. They can be viewed and processed in the admin panel by users with the '''Manage Reports''' power.
 ==Submission==
@@ Line 25: / Line 25: @@
 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.
-=== Assigning Reports ===
+===Assigning Reports===
 Newly submitted reports are "unassigned"; that is, there is no user assigned to handling them. Any user with the Manage Reports power can assign an unassigned report to themself. This removes the report from the main queue and places it into a special user-specific queue section that displays only the assigned reports for the currently logged-in user, the status of which is reflected on the admin index. Permissioned users may still view all current assigned reports via the queue.
-=== Processing ===
+===Processing===
 Open reports can be commented on by staff and user(s). This can be used to communicate with user(s) in order to facilitate addressing the subject of the report.
 Once the subject of a report is resolved, it can be closed with staff notes as to any pertinent details, such as action taken. Once a report is closed, users will not be able to view comments on the report, though they will remain visible to staff, so any details that should be preserved from comments should be included in the staff notes.
-== Bug Report Index ==
+==Bug Report Index==
 A site's bug reports are listed publicly in its bug report index. This list shows the title of the report, when it was submitted, and its status. This list may be searched by URL or title. Logged-in users may view the details of non-exploit bug reports; exploit reports, however, are hidden until they are closed to prevent abuse.

@@ Line 18: / Line 18: @@
 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 ==
+==Report Queue==
 Users with the '''Manage Reports''' power can view the queue, assign themselves to reports, respond as appropriate, and close reports.
@@ Line 24: / Line 24: @@
 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]]

@@ 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.
-=== Submission ===
+===Submission===
-Reports submitted to the queue cannot be edited by the user.<br />
+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).
+*
 [[Category:Documentation]]

@@ Line 13: / Line 13: @@
 **The type of error being reported. By default, the options are: 500 error, 404 error, text error, exploit, or other error.
 *'''Comments'''
-**<br />
+**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.
-***
 [[Category:Documentation]]

@@ Line 1: / Line 1: @@
 Reports are a submission type added in [[Updating: to 2.0.0|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 ==
+==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'''
+*'''URL/Title'''
-** Either a link to offending content (content report) or a short summary of the bug (bug report)
+**Either a link to offending content (content report) or a short summary of the bug (bug report)
-* '''Is/Is Not Bug Report (Toggle)'''
+*'''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.
+**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)'''
+*'''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.
 [[Category:Documentation]]

← Older revision		Revision as of 16:29, 16 July 2021
Line 1:		Line 1:
	Reports are a submission type added in [[Updating: to 2.0.0\|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.		Reports are a submission type added in [[Updating: to 2.0.0\|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)'''
		+	**
		+
	[[Category:Documentation]]		[[Category:Documentation]]

← Older revision	Revision as of 16:24, 16 July 2021
(No difference)