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

Show available IP's with read-only access to Prefixes #8839

New Issue
Closed
opened 2025-12-29 20:41:56 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:41:56 +01:00
Owner
Copy Link

Originally created by @woodgre on GitHub (Nov 15, 2023).

NetBox version

v3.6.5

Feature type

Change to existing functionality

Proposed functionality

If you have read/write access to Prefixes, you will see highlighted examples of available IP's for consumption:

image

However, the consumers of this tool who will want to find an available IP - do not manage prefixes, and only have read access to them: they don't see the available IP's, even though clicking on one of the green links does not need Prefix write access.

image

Use case

Having the green links available for IP consumption is one of the best features of netbox - but in my opinion, should not require write access to Prefixes.

Database changes

This is purely a UI change. I can't fathom any database changes needed.

External dependencies

None.

Originally created by @woodgre on GitHub (Nov 15, 2023). ### NetBox version v3.6.5 ### Feature type Change to existing functionality ### Proposed functionality If you have read/write access to Prefixes, you will see highlighted examples of available IP's for consumption: ![image](https://github.com/netbox-community/netbox/assets/66434022/d436b936-7580-43dd-a298-b33ccfe48b1a) However, the consumers of this tool who will want to find an available IP - do not manage prefixes, and only have read access to them: they don't see the available IP's, even though clicking on one of the green links does not need Prefix write access. ![image](https://github.com/netbox-community/netbox/assets/66434022/0d3a800c-44df-4e82-952a-2f3ab2c709a4) ### Use case Having the green links available for IP consumption is one of the _**best features**_ of netbox - but in my opinion, should not require write access to Prefixes. ### Database changes This is purely a UI change. I can't fathom any database changes needed. ### External dependencies None.
adam added the type: feature label 2025-12-29 20:41:56 +01:00
adam closed this issue 2025-12-29 20:41:56 +01:00
adam commented 2025-12-29 20:41:56 +01:00
Author
Owner
Copy Link

@woodgre commented on GitHub (Nov 15, 2023):

NM, Pebkac. the sample user somehow had a display preference to hide this feature and I erroneously attributed it to permissions.

@woodgre commented on GitHub (Nov 15, 2023): NM, Pebkac. the sample user somehow had a display preference to hide this feature and I erroneously attributed it to permissions.
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 type: feature
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#8839
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?