View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 375 | Composr | tickets | public | 2012-01-08 01:59 | 2016-11-03 04:03 |
| Reporter | Chris Graham | Assigned To | Chris Graham | ||
| Priority | normal | Severity | feature | ||
| Status | resolved | Resolution | fixed | ||
| Summary | 375: Change reported posts addon to general reporting addon, and merge with tickets | ||||
| Description | Rip out this code from Conversr, and merge with the non-bundled reportcontent addon. No reported content or reported posts forums anymore though, just use tickets as the storage mechanism. This isn't a huge change as tickets are forum based too. Report content and report post functionality all therefore becomes a part of the ticket system. This simplifies and streamlines. Delete extraneous code/addons once functionality is moved. Make sure docs are clearly updated to not refer to a separated reported posts forum. Update the ticket system documentation to clearly say it includes report content functionality. Remove 'cns_reported_posts' from the tracker. | ||||
| Additional Information | I've attached Patrick's alpha code TAR, which I'll likely heavily rework. He said: "This is a TAR of my reported content addon with the support tickets integration, anonymous reporting, inclusion of content in reports, duplicate report checking, and other tweaks." | ||||
| Tags | Risk: Deprecates functionality , Risk: Major rearchitecting | ||||
| Attach Tags | |||||
| Attached Files | |||||
| Time estimation (hours) | 8 | ||||
| Sponsorship open | |||||
| related to | 2911 | Resolved | Chris Graham | Merge messaging system with tickets system |
|
|
Side note for Chris + public: alpha code has not been run through coding standards checklist. It does work with some tweaking but highly not recommended for production site. |
|
|
I've been through very careful. The final result is pretty different to your code because the tickets API just went through a huge cleanup to make things more elegant. Functionally it's very similar. I didn't add a ticket_id field to the reported_content table because we're now generating semantic ticket IDs matching the content being reported. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-06-08 00:14 | Chris Graham | Tag Renamed | Major rearchitecting => Risk: Major rearchitecting |
| 2016-06-08 00:15 | Chris Graham | Tag Renamed | Deprecates functionality => Risk: Deprecates functionality |
| 2016-10-29 23:39 | Chris Graham | Description Updated | |
| 2016-10-29 23:39 | Chris Graham | Additional Information Updated | |
| 2016-10-29 23:39 | Chris Graham | File Added: reported_content_4.tar | |
| 2016-10-29 23:41 | Chris Graham | Summary | Change reported posts addon to general reporting addon => Change reported posts addon to general reporting addon, and merge with tickets |
| 2016-10-29 23:41 | Chris Graham | Description Updated | |
| 2016-10-29 23:41 | Chris Graham | Time estimation (hours) | 3 => 8 |
| 2016-10-29 23:42 | Chris Graham | Category | cns_reported_posts => tickets |
| 2016-10-29 23:42 | Chris Graham | Description Updated | |
| 2016-10-29 23:43 | Chris Graham | Relationship added | related to 2911 |
| 2016-10-30 00:25 | PDStig | Note Added: 0004504 | |
| 2016-11-03 04:01 | Chris Graham | Status | Not Assigned => Resolved |
| 2016-11-03 04:01 | Chris Graham | Resolution | open => fixed |
| 2016-11-03 04:01 | Chris Graham | Assigned To | => Chris Graham |
| 2016-11-03 04:03 | Chris Graham | Note Added: 0004512 |
