Assignment validation requires the url part associated with the assignment to be unique within a course, which effectively requires assignment short names to be universally unique across all offerings of a course.
Coupled with this, there does not appear to be any obvious way to re-offer an existing assignment in a new course offering in a later semester.
The net effect is that, if someone teaching course X using "Project 1" as their assignment name, no later instructors can ever use that same name for their own assignments.
This issue is intertwined with the friendly urls controller, and how urls are used to encode assignment information. It is also intertwined with how repositories are located on disk. Unfortunately, the restrictions it imposes seem too severe, so these issues have to be disentangled (for example: use assignment database ids as part of repo directory names on disk--e.g., short-name/id/...--plus use course offering to disambiguate short names in friendly urls, then restrict assignments to only have unique url parts among all the assignments in all the course offerings they are offered in, instead of globally for the course?).
Assignment validation requires the url part associated with the assignment to be unique within a course, which effectively requires assignment short names to be universally unique across all offerings of a course.
Coupled with this, there does not appear to be any obvious way to re-offer an existing assignment in a new course offering in a later semester.
The net effect is that, if someone teaching course X using "Project 1" as their assignment name, no later instructors can ever use that same name for their own assignments.
This issue is intertwined with the friendly urls controller, and how urls are used to encode assignment information. It is also intertwined with how repositories are located on disk. Unfortunately, the restrictions it imposes seem too severe, so these issues have to be disentangled (for example: use assignment database ids as part of repo directory names on disk--e.g., short-name/id/...--plus use course offering to disambiguate short names in friendly urls, then restrict assignments to only have unique url parts among all the assignments in all the course offerings they are offered in, instead of globally for the course?).