-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
false positive related object in custom fields #15548
Comments
This is not that it is bound to a specific object, it is just stating that the custom field has a relation to the django content type table. Technically, it is not incorrect, but I agree we should probably exempt the contenttype field from the relationship check on deletion, at least for this specific case. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Could you please assign it to me? |
Deployment Type
Self-hosted
NetBox Version
v3.7.4
Python Version
3.10
Steps to Reproduce
Expected Behavior
Newly created custom field isn't bound to any object, so user should get simple delete confirmation dialog without related objects.
Observed Behavior
User gets delete confirmation dialog with related objects even though those kinds of objects don't exist.
Another observation, don't know if it is this issue related:
During the upgrade procedure to the feature branch, I get the following error mentioning the customfield_content_types:
The text was updated successfully, but these errors were encountered: