Damith C. Rajapakse

> @damithc we need to play devil's advocate here. We can't please every single user. Do we want to prioritize "easier edit after submission" or "go to other page but...

> Should I try to make the frontend changes and see how it goes? > > After the PR is up, we can discuss if we want to merge it....

We already show this to the user  Showing similar messages in each question _might_ help a bit (while adding more verbosity) but the issue here is that the form...

> Hello prof, may I ask if the green background for the header & tick for each question will persistent (i.e. If user comes back another time to edit his/her...

@domlimm persistent doesn't mean saving it as a separate field in the database. The front end should be able to determine which answers were loaded from the database (and hence,...

> @damithc Regarding the cloned course, may I confirm that all it retains from the original are the sessions and the questions? @moziliar I can think of improving this feature...

> @damithc In addition to what is already done in #11012, do you want to allow instructors to copy from other courses when they are creating new courses? (there is...

> @damithc I think we can update the details to be editable, and since we already have the API to update instructors, we only need to update the frontend, unless...

> @damithc we have `updateInstructorCascade`, so the changes will be propagated everywhere I see. Just to check, suppose I'm fixing a typo in the institute name. Does the change propagate...

> Comments, responses and deadline extensions will be updated if instructor is updated > Fixing institute name = updating courses, and similarly we have `updateCourseCascade` for this, so yes the...