CSC/ECE 517 Fall 2015 E1584 Send Feedback to Support: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
Line 14: Line 14:
The following specifications are required in the feature :
The following specifications are required in the feature :


*Support feature for Users  
* Support feature for Users  
** The link to "Contact Support" should be present in the '''title bar'''. This should help facilitate feedback from un-logged users.
** The link to "Contact Support" should be present in the '''title bar'''. This should help facilitate feedback from un-logged users.
** Clicking on "Contact Support" should open a '''new page''' rather than a pop-up or modal dialog box.
** Clicking on "Contact Support" should open a '''new page''' rather than a pop-up or modal dialog box.
** The feedback form should consist of the following fields: '''Email''', '''Name''' (optional), '''Title''', '''Description''' (optional) and '''Attachments'''(optional).
** The feedback form should consist of the following fields: '''Email''', '''Name''' (optional), '''Title''', '''Description''' (optional) and '''Attachments'''(optional).
** The feedback should go '''expertiza-support@lists.ncsu.edu'''.
** The feedback should go '''expertiza-support@lists.ncsu.edu'''.
** Users should should have the facility to '''upload''' only one file in their feedback.  
** Users should should have the facility to upload '''only one file''' in their feedback.  
** The uploaded file should be either in '''.pdf or .png/.jpg''' format. Moreover, the extension list should not be hard-coded. A '''white-list''' of the extensions supported, should be present in the database.   
** The uploaded file should be either in '''.pdf or .png/.jpg''' format. Moreover, the extension list should not be hard-coded. A '''white-list''' of the extensions supported should be present in the database.   
** The size of the uploaded file should '''not exceed 2MB'''.
** The size of the uploaded file should '''not exceed 2MB'''.
** To avoid attacks, the feedback form should contain a '''CAPTCHA'''.
** To avoid attacks, the feedback form should contain a '''CAPTCHA'''.
** There should be a separate method that keeps a check on '''multiple requests'''. An algorithm should be implemented to add incremental delay between consecutive requests after three trials.
** There should be a separate method that keeps a check on '''multiple requests'''. An algorithm should be implemented to add incremental delay between consecutive requests after three trials.
* Support feature for support people
** The link to "Feedback" should be present in the title bar under the "Contact Us" heading.
** Only people who are assigned the role as '''support''' will be able to use view the link.
** The feedback page should contain a list of all the issues in a '''table format'''.
** Each feedback can be categorized into the following state:
*** '''Open''' - when a new feedback is generated by the user and not yet handled by any support person.
*** '''In Progress''' - when a support person has viewed the feedback and started working on it.
*** '''Closed''' - when a support person has solved the issue in the feedback.
*** '''Invalid''' - when the feedback is not relevant to Expertiza.


= Proposed Implementation =
= Proposed Implementation =

Revision as of 18:24, 10 November 2015

E1584. Send Feedback to Support

This is the design document for the Feedback to Support feature of Expertiza.

Introduction

Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities. <ref>Expertiza on GitHub</ref>

Problem Statement

The objective of this project is to allow Expertiza users to directly send their issues to Expertiza support via support form. Currently there is no support feature and the problems are passed on to the support people via instructors. The aim of this feature is faster resolution of the problems faced by the users. This feature should be available to all registered users and the users should have access to it even when they are not logged in. Moreover, it should also allow users to send screenshots of their issues. Apart from the feedback form, a view for the support person is also required. This view would contain a collective list of all the problems and the support person would be able to change the status of the problems.

Design Specification

The following specifications are required in the feature :

  • Support feature for Users
    • The link to "Contact Support" should be present in the title bar. This should help facilitate feedback from un-logged users.
    • Clicking on "Contact Support" should open a new page rather than a pop-up or modal dialog box.
    • The feedback form should consist of the following fields: Email, Name (optional), Title, Description (optional) and Attachments(optional).
    • The feedback should go expertiza-support@lists.ncsu.edu.
    • Users should should have the facility to upload only one file in their feedback.
    • The uploaded file should be either in .pdf or .png/.jpg format. Moreover, the extension list should not be hard-coded. A white-list of the extensions supported should be present in the database.
    • The size of the uploaded file should not exceed 2MB.
    • To avoid attacks, the feedback form should contain a CAPTCHA.
    • There should be a separate method that keeps a check on multiple requests. An algorithm should be implemented to add incremental delay between consecutive requests after three trials.
  • Support feature for support people
    • The link to "Feedback" should be present in the title bar under the "Contact Us" heading.
    • Only people who are assigned the role as support will be able to use view the link.
    • The feedback page should contain a list of all the issues in a table format.
    • Each feedback can be categorized into the following state:
      • Open - when a new feedback is generated by the user and not yet handled by any support person.
      • In Progress - when a support person has viewed the feedback and started working on it.
      • Closed - when a support person has solved the issue in the feedback.
      • Invalid - when the feedback is not relevant to Expertiza.

Proposed Implementation

Mock Ups

References

<references/>