Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected behavior when selecting multiple feedback question recipients #11474

Closed
tjtanjin opened this issue Nov 18, 2021 · 3 comments · Fixed by #11480
Closed

Unexpected behavior when selecting multiple feedback question recipients #11474

tjtanjin opened this issue Nov 18, 2021 · 3 comments · Fixed by #11480
Labels
c.Bug Bug/defect report p.Urgent Would like to handle in the very next release

Comments

@tjtanjin
Copy link
Contributor

Reproduced on local dev environment on commit a5fe4b0

Steps to reproduce

  1. Go to instructor sessions page
  2. Edit a question and change recipient to other students in the course
  3. Try to set the maximum number of students feedback should be given to
  4. Save the changes and refresh the page - notice changes are not saved

More elaborate examples shown below:

Question 1 is being used for testing here, I tried changing the maximum number of students but even though the value supposedly saves, a refresh shows otherwise.

unable_to_change_limit_value.mp4

Question 2 is being used for testing here, this time, I cannot even modify the maximum number of students. I can however, still save it but refreshing reverts the choice to unlimited again.

unable_to_choose_max_option.mp4

Additional info
Strangely, I cannot spot any noticeable difference between the 2 question types. In fact, question 1 was initially having the exact same issue as question 2 and simply suddenly changed its behaviour as I continued testing. I am unable to specifically reproduce the two differing behaviours though they are likely to have the same source of bug.

@damithc damithc added p.Urgent Would like to handle in the very next release c.Bug Bug/defect report labels Nov 19, 2021
@damithc
Copy link
Contributor

damithc commented Nov 19, 2021

Looks like a serious bug. Would like to fix before the next release, plus this is holding us back from doing a release. Alternatively, we can revert the problematic PR for now, if that can be done cleanly.

@wkurniawan07
Copy link
Member

@tjtanjin I got a good idea as to why it happened. Can you help to verify that the changes introduced in this branch https://github.com/TEAMMATES/teammates/tree/11474-feedback-path-event-bubbleup-error fixed the problem?

@tjtanjin
Copy link
Contributor Author

@tjtanjin I got a good idea as to why it happened. Can you help to verify that the changes introduced in this branch https://github.com/TEAMMATES/teammates/tree/11474-feedback-path-event-bubbleup-error fixed the problem?

Hello! I have tested and the changes introduced in this branch fixes the problem!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c.Bug Bug/defect report p.Urgent Would like to handle in the very next release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants