What problem are you trying to solve with Submitty
When creating a gradeable, the current process to set the dates is really tedious and confusing. Changing one date could cause a lot of red boxes to appear over other dates (For example, setting the due date past the TA grading date would cause that date to get highlighted red), and as a result the gradeable can't be saved since these are database constraints.
Example of red boxes appearing with invalid dates:
Example of warning message appearing instead of database constraints for grade inquiries (Already fixed):
Describe the way you'd like to solve this problem
A way I would like to solve this problem is to simply remove the database constraints entirely. Instead of having database constraints and red boxes, the instructor can set the dates to whatever they want to, and if they set an invalid date, a warning message will simply appear on the top of the screen stating what issues that may cause.
Describe any potential alternatives you'd tried to solve the problem
We tried still keeping the constraints and moving all the conflicting dates foreword when a specific date was changed. The issue with this is that a professor may accidently move a specific date forward by a massive amount of time, causing all the other dates to be moved forward unintentionally and causing frustration to the instructor.
Additional context
This problem will be solved in smaller iterations. The first iteration will be removing the date constraints for TA Beta testing, and ensuring that it works. The rest of the date constraints will follow. Each iteration will need to be thoroughly tested and work with one date at a time to ensure nothing breaks.
What problem are you trying to solve with Submitty
When creating a gradeable, the current process to set the dates is really tedious and confusing. Changing one date could cause a lot of red boxes to appear over other dates (For example, setting the due date past the TA grading date would cause that date to get highlighted red), and as a result the gradeable can't be saved since these are database constraints.
Example of red boxes appearing with invalid dates:
Example of warning message appearing instead of database constraints for grade inquiries (Already fixed):
Describe the way you'd like to solve this problem
A way I would like to solve this problem is to simply remove the database constraints entirely. Instead of having database constraints and red boxes, the instructor can set the dates to whatever they want to, and if they set an invalid date, a warning message will simply appear on the top of the screen stating what issues that may cause.
Describe any potential alternatives you'd tried to solve the problem
We tried still keeping the constraints and moving all the conflicting dates foreword when a specific date was changed. The issue with this is that a professor may accidently move a specific date forward by a massive amount of time, causing all the other dates to be moved forward unintentionally and causing frustration to the instructor.
Additional context
This problem will be solved in smaller iterations. The first iteration will be removing the date constraints for TA Beta testing, and ensuring that it works. The rest of the date constraints will follow. Each iteration will need to be thoroughly tested and work with one date at a time to ensure nothing breaks.