Closed joshuarusso closed 10 years ago
How about adding a group identifier to the end of the name? I built in the prevention of duplicate names to address the following scenario:
Let's say you want to add a task to a group or a user. How would you know which one to pick if there are duplicate names?
There are plenty of other issues with duplicate names but this is one example. Th
Hmm gotcha. Issues would be via usability and auto implementation. If the task name has the group id, it will be super long for the SMS/Email, and also for use within the system on a daily basis.
Could we resolve it via the following?
For the user, task names can be replicated.
For the system, the task name is actually a combination between the group identifier and the the task name. But the user would only see the task name - as they would be sorting by group and see the group as a separate field.
Would this solve the problem? And also allow us to upload duplicate task items.
This is possible. I will work on it and send out an update when it's ready!
Done. Took longer than I do to the new input design necessary
Two courses have the same task names. Eg: SAT Fundamentals Class 1 - but the system is preventing the upload of the duplicates, even though the Groups are different. Any ideas on this?