starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Can not create rack reservation without rights to read all system users #10242

New Issue
Closed
opened 2025-12-29 21:28:46 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:28:46 +01:00
Owner
Copy Link

Originally created by @stavr666 on GitHub (Sep 13, 2024).

Deployment Type

NetBox Cloud

NetBox Version

v4.0.8

Python Version

3.11

Steps to Reproduce

  1. Create permission set with view+add+change+delete rights to devices, racks and rack reservations
  2. Assign permission set to new user (without any other rights)
  3. As created user try to make new reservation to any rack

Expected Behavior

User can create reservation to herself.
Null-valued field "user" acceptable and interpreted by the system as "reservation assigned to me" without knowing how many users in system.

Observed Behavior

During reservation process field "user" is required and admin must add user access to (full?) list for any operations requiring this field.
image

Bug reproducible in 4.1.1 demo.

Originally created by @stavr666 on GitHub (Sep 13, 2024). ### Deployment Type NetBox Cloud ### NetBox Version v4.0.8 ### Python Version 3.11 ### Steps to Reproduce 1. Create permission set with view+add+change+delete rights to devices, racks and rack reservations 2. Assign permission set to new user (without any other rights) 3. As created user try to make new reservation to any rack ### Expected Behavior User can create reservation to herself. Null-valued field "user" acceptable and interpreted by the system as "reservation assigned to me" without knowing how many users in system. ### Observed Behavior During reservation process field "user" is required and admin must add user access to (full?) list for any operations requiring this field. ![image](https://github.com/user-attachments/assets/0af65507-146f-4f3f-a0b3-12bec0392536) Bug reproducible in 4.1.1 demo.
adam closed this issue 2025-12-29 21:28:46 +01:00
adam commented 2025-12-29 21:28:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 13, 2024):

This is not a bug. If you want to limit the set of users to which one user may assign a reservation, you can use permission constraints to do so.

@jeremystretch commented on GitHub (Sep 13, 2024): This is not a bug. If you want to limit the set of users to which one user may assign a reservation, you can use [permission constraints](https://netboxlabs.com/docs/netbox/en/stable/administration/permissions/#constraints) to do so.
adam commented 2025-12-29 21:28:47 +01:00
Author
Owner
Copy Link

@stavr666 commented on GitHub (Sep 16, 2024):

This is not a bug. If you want to limit the set of users to which one user may assign a reservation, you can use permission constraints to do so.

I wish that every user could create reservation, as long as he have access to CREATE RESERVATION. As it was in 3.0.
Without giving access to full list of users. As it required now without any reason (when this is not required).

P.S. I wish to limit set of users, who can fish every Netbox user logon.

@stavr666 commented on GitHub (Sep 16, 2024): > This is not a bug. If you want to limit the set of users to which one user may assign a reservation, you can use [permission constraints](https://netboxlabs.com/docs/netbox/en/stable/administration/permissions/#constraints) to do so. I wish that every user could create reservation, as long as he have access to CREATE RESERVATION. As it was in 3.0. Without giving access to full list of users. As it **required** now without any reason (when this is not required). P.S. I wish to limit set of users, who can fish every Netbox user logon.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10242
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?