We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
We noticed that the wrong user was being displayed in the assignment dropdown in the inspector form.
Looking in the database, we figured out that the user_id value in user_planned_reports referenced a user that has been anonymized.
user_id
user_planned_reports
To Reproduce
Steps to reproduce the behavior:
Expected behavior
That the assignment dropdown displays “unassigned”.
Screenshots
N/A
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
It seems to me that the dropdown should be able to handle anonymized users or that anonymized users should be unassigned.
The former option retains more information.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
We noticed that the wrong user was being displayed in the assignment dropdown in the inspector form.
Looking in the database, we figured out that the
user_id
value inuser_planned_reports
referenced a user that has been anonymized.To Reproduce
Steps to reproduce the behavior:
Expected behavior
That the assignment dropdown displays “unassigned”.
Screenshots
N/A
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
It seems to me that the dropdown should be able to handle anonymized users or that anonymized users should be unassigned.
The former option retains more information.
The text was updated successfully, but these errors were encountered: