Support/Live Chat/Web Client PRD: Difference between revisions

category -> Support Archive
(category -> Support Archive)
 
(5 intermediate revisions by 4 users not shown)
Line 1: Line 1:
==OBSOLETE PAGE==
use [https://wiki.mozilla.org/Support/Live_Chat Support/Live Chat]
==Introduction==
==Introduction==


Line 39: Line 42:
** All chats displayed in a single tabbed interface, animated via jquery, with basic notification of active tabs.
** All chats displayed in a single tabbed interface, animated via jquery, with basic notification of active tabs.


==Requirements, milestone 1==
==Requirements, milestone 1 (Quarter 3, 2009)==
* Should use the existing [http://viewvc.svn.mozilla.org/vc/projects/livechat/trunk/webchat Fastpath Webchat] framework to save time and make use of existing Fastpath functionality.
* Should use the existing [http://viewvc.svn.mozilla.org/vc/projects/livechat/trunk/webchat Fastpath Webchat] framework to save time and make use of existing Fastpath functionality.
** This client is currently structured as a Java Servlet which uses '''Smack''' to make connections to an Openfire XMPP server.  All interaction with the web client is currently through simple JSP pages that use [http://www.directwebremoting.org DWR] for communication with the servlet.
** This client is currently structured as a Java Servlet which uses '''Smack''' to make connections to an Openfire XMPP server.  All interaction with the web client is currently through simple JSP pages that use [http://www.directwebremoting.org DWR] for communication with the servlet.
Line 76: Line 79:
** UI for setting maxchats.
** UI for setting maxchats.


==Requirements, milestone 3==
== Requirements, milestone 3 ==
* Should be stable and comfortable to use on a daily basis
 
* Color coded chat tabs to allow agents to reply to older messages first.
*Should be stable and comfortable to use on a daily basis  
* Style of client should be defined in a theme, with users able to select a theme when connecting
*Color coded chat tabs to allow agents to reply to older messages first.
* Integrate with SUMO karma
*All milestone 1-2 features should be functional and QA tested, with no regressions from Spark.  
* All milestone 1-2 features should be functional and QA tested, with no regressions from Spark.
*Integration with modules from Contributor Home Page. (Show modules in web client when live chat is closed, and show chat status on contributor home page)
* Integration with modules from Contributor Home Page. (Show modules in web client when live chat is closed, and show chat status on contributor home page)


==Requirements, future==
==Requirements, future==
Line 159: Line 161:
** Embed a rotation of objects from Contributor Home Page (eg. forum posts) when chat is closed.
** Embed a rotation of objects from Contributor Home Page (eg. forum posts) when chat is closed.
* Testing, bug fixing, polish, UI (at least 10 hours)
* Testing, bug fixing, polish, UI (at least 10 hours)
[[Category:Support Archive]]
1,241

edits