Project

General

Profile

Bug #1365

Assignment tool with Groups: risk of losing student work

Added by Jan Derriks over 9 years ago. Updated over 9 years ago.

Status:
Feature implemented
Priority:
High
Category:
-
Target version:
Start date:
27/05/2010
Due date:
% Done:

100%

Estimated time:
Complexity:
Normal
SCRUM pts - complexity:
3

Description

The group tool combined with assignments and grading is a powerful combination but it is buggy.
The problem is that the name of an assignment must be unique within a course, even if the assignment is given to different groups.
Now Chamilo will help you and automatically add a number to the name of an assignment if it already exist but unfortunately many teachers are pretty stubborn and sometimes do something dramatically: they change the name of the assignment and remove the number they did not type.
This has terrible consequences: reports already handed in disappear from the assignment (though they are not really gone)or groups that shouldn't see an assignment now do see them, with reports and all.
If this happens you carefully need to rename the assignments back to the original name or hack the assignment file structure in the database to make it all visible again.

Even if you don't use groups you can reproduce trhe problem:
1. create an assignment called ONE
2. create a second assignment called ONE - (it will be named ONE1 automatically)
3. thow a paper in ONE and ONE1
4. rename ONE1 into ONE and refresh the browser window - the paper titles are now both visible in the ONE assignment... but:
5. try to view the paper that was in ONE1 and it will seem empty because chamilo will look in the wrong curDirPath url.

Possible solutions:
- Assignment names should not be used as "primary keys" into assignment folders. Add a hash.
- rename of assignment should not allow duplicate assignment name (easy to code but not userfriendly).

(related: work on Feature #1210)

History

#1

Updated by Yannick Warnier over 9 years ago

  • Status changed from New to Assigned
  • Assignee set to Julio Montoya
  • Priority changed from Normal to High
  • SCRUM pts - complexity changed from ? to 3
#2

Updated by Julio Montoya over 9 years ago

I confirm this bug

#3

Updated by Julio Montoya over 9 years ago

Since we can make changs to the database and we are going to release 1.8.7 soon I will take the second option:

- rename of assignment should not allow duplicate assignment name (easy to code but not userfriendly).

This task after that this task should be move to 1.8.7.1 or whatever the name is to use primary keys instead the curdirpath

#4

Updated by Julio Montoya over 9 years ago

  • Status changed from Assigned to Needs testing
  • Assignee changed from Julio Montoya to Curt Ricardo Rodriguez Salazar
#5

Updated by Curt Ricardo Rodriguez Salazar over 9 years ago

  • Status changed from Needs testing to Feature implemented
  • % Done changed from 0 to 100

when you create a second assignment called ONE - (it will be named ONE1 automatically)... now, can't be rename automatically, which means that the bugs were fixed.

Also available in: Atom PDF