-
Notifications
You must be signed in to change notification settings - Fork 154
Incorrect Reference "department" in request model #144
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
Comments
No. Group is a parent model for the Department. Department should be added as Department, not a Group. |
I have avery similar error, even when creating the request with a user with the role of operator or manager. When I try to create a request, the department select does not show the departments associated with the user, whether they have multiple or just one. Also, no options appear in the owner dropdown. |
That's because you used the Admin site. |
There is something odd with the "department" field in the Requests model.
information about test parameter:
How to reproduce the bug:
? is it correct that the "department" i a "group"?
This results in this:
FYI:
the department field is not part of the requests model but the inherited model Base1. There department is defined like this:
is it even required to have department as an mandatory field in request model (in Base1 it is marked as null=True)?
PS: maybe it is an MSSQL problem? MSSQL is not capable of doing database-side regular expressions. I already transferred one on python side to make it compatible. Maybe department also uses regular expressions to filter?
PPS: I think it is a permission problem. I had a superuser with blank groups and permissions. Now I added every permission to my user and now I see something in the departments dropdown.
The text was updated successfully, but these errors were encountered: