Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. (minus) JIRA bugs and issues remaining from 0.7 (assigned within JIRA)
    1. (tick) http://bugs.sakaiproject.org/jira/browse/EVALSYS-85
    2. (tick) http://bugs.sakaiproject.org/jira/browse/EVALSYS-84
    3. (tick) http://bugs.sakaiproject.org/jira/browse/EVALSYS-81
    4. (tick) http://bugs.sakaiproject.org/jira/browse/EVALSYS-83
    5. http://bugs.sakaiproject.org/jira/browse/EVALSYS-82
    6. http://bugs.sakaiproject.org/jira/browse/EVALSYS-73
    7. (tick) http://bugs.sakaiproject.org/jira/browse/EVALSYS-72
    8. (tick) http://bugs.sakaiproject.org/jira/browse/EVALSYS-27
  2. (minus) Expert Items ~aaronz
    1. Templates for the expert item process
    2. Preload a small set of expert items
    3. Producers for expert items
    4. Expert item creation (admin tool)
  3. (minus) Existing items
    1. Change control panel to a "templates" and "evaluations" view
    2. Create "items" view to support choosing and listing existing items
    3. Allow users to reuse existing items (except block parents)
    4. Allow users to remove unlocked items
  4. (minus) Allow instructors to add items to evaluations assigned to them
    1. Create new view from wireframe
    2. Use basic hierarchy code
    3. Update the logic layer to return the instructor related items
    4. Update everything that gets templateitems to use the logic layer and not the lazy loaded list from the hibernate object
  5. (tick) Administrative Tools ~kapsahuja22
    1. (tick) Remove scale - EVALSYS-95
    2. (tick) Modify scale - EVALSYS-16 (carry over task EVALSYS-99 assigned to Antranig).
    3. (tick) Add scale - EVALSYS-96 (carry over task EVALSYS-99 assigned to Antranig).
  6. (info) Administrative Tools - EVALSYS-99 - Antranig.
  7. (error) User input ~kapsahuja22 - to be carried over to 0.9 release
    1. Make sure dates are input using a date widget
    2. Make sure text is input using WYSIWYG
    3. Make sure no user input can cause XSS attacks
    4. Check that no user input can cause an exception
  8. (minus) Email functionality (continued) ~rwellis
    1. Scheduling emails (Quartz scheduler)
    2. Links in emails work to take an eval
  9. (minus) Scheduling for evals (registering start, due, etc...) and switching eval states ~rwellis
    1. Scheduling evaluation state changes (inQueue -> Active -> Due -> Closed -> Viewable)
  10. (minus) Test external contexts providers ~rmoyer@umd.edu
  11. (minus) AJAX reordering ~spfjr@umd.edu
    1. reordering of template items on the modify template items view
    2. reordering of template items within a block in the modify block view
  12. (minus) (info) Ensure that all current functionality is working ~fengr@vt.edu, Lisa-UM?
    1. verify that i18n applied to all strings
    2. verify that no broken links or buttons exist on any page
    3. check that user cannot cause exceptions with input
    4. check that no exceptions occur

...