149: Integrated issue logging - Composr CMS feature tracker

ID	Project	Category	View Status	Date Submitted	Last Update

149	Composr	core	public	2010-04-07 22:47	2011-03-23 16:54

Reporter	Chris Graham	Assigned To	Chris Graham
Priority	normal	Severity	feature
Status	closed	Resolution	no change required

Summary	149: Integrated issue logging
Description	Implement AJAX pin API on our server (will need a relay script to get past domain restrictions). Fully 'wikify' movement/deletion of the pins (by storing the data on a special CEDI page). Allow pins to go to the issue logger, CEDI, forum topics, or local forum topics. Have different pin icons for each annotation type. In Composr: - pin system. People can add a pin to a number of "planes" with pins - activation button listed in the bottom buttons - planes and pin counts listed on help panel - shared planes [grabbed via web services - no assumptions hard-coded into cms] - any number of within-single-site planes - pins tied to a match-key (default detected via a simplification of current page-link) - default may be adjusted - for within-site planes, the match-key includes ID's of content screens, otherwise does not - pins may stand alone, or link to a CEDI page or link to a forum topic or link to tracker issue; for shared ones these are on our site, otherwise they are on users site. Topic/CEDI page association should be automatic (creates topic/CEDI post via web service) - but then customisable. - CEDI stuff created under a CEDI subtree associated with the pin layer - topics/CEDI stuff should all be easily accessible from compo.sr, and show summaries of the pins they are assigned to and a little feature to jump to them for the base URL someone has listed in their member profile (but can be adjusted at point of clicking - the member profile option just defines the default) - all pin data must be stored actually via topic/CEDI backend: i.e. you should be able to fully edit by using your moderation access on compo.sr (if you have them - and I think we'll grant it) - likewise, ability to edit pins via dragging them around, deleting them, etc, would be restrtricted by permissions - working via a web service - set up a default CEDI tree with some default pins on various layers, to start it up.
Additional Information	This is all an important part of our way we are going to open the door to better usability and support, by creating a system where people have full access to engage with our process and provide quick&easy structured feedback. It's a way to harness the 'wisdom of crowds' that hopefully gets past people's natural inertia.
Tags	Risk: Database change , Skills: Graphic design , Skills: Lead programming
Attach Tags	(Separate by ",")

Time estimation (hours)	20
Sponsorship open

Date Added	Member	Amount Sponsored

Chris Graham 2010-11-29 00:44 administrator ~101	Possibly integrate something like Zoho Chat (http://chat.zoho.com/) so people can share screenshots and chat amongst themselves whilst using Composr. http://www.readwriteweb.com/archives/10_chat_widgets.php

Chris Graham 2011-03-23 16:54 administrator ~126	The integrated chat room has been added. Generally usability and general system cohesion is improved a lot since this idea came up and the pin idea will cause more confusion than it'll help.

Date Modified	Username	Field	Change
2016-06-08 00:15	Chris Graham	Tag Renamed	Database change => Risk: Database change