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

X IPs available sorting not resetable from IPAM -> Prefixes -> (prefix) -> IP Addresses menu #6468

New Issue
Closed
opened 2025-12-29 19:41:03 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:41:03 +01:00
Owner
Copy Link

Originally created by @Azbests on GitHub (May 10, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.2.2

Python version

3.8

Steps to Reproduce

  1. Go to IPAM -> Prefixes -> (prefix) -> IP Addresses
  2. Resort table by any of columns

Expected Behavior

X IPs available should be above/below/in-middle where needed.

Observed Behavior

X IPs available now are sorted like standard entries and are always positioned above/below in ip list. And there is no way to reset this view from this table.

image

Note: There is a work around suggested by Simon T to clear table preferences for IPAddressTable in /user/preferences/. Which will return this table to default sorting with X IPs available positioned correctly.

Originally created by @Azbests on GitHub (May 10, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.2.2 ### Python version 3.8 ### Steps to Reproduce 1. Go to `IPAM -> Prefixes -> (prefix) -> IP Addresses` 2. Resort table by any of columns ### Expected Behavior `X IPs available` should be above/below/in-middle where needed. ### Observed Behavior `X IPs available` now are sorted like standard entries and are always positioned above/below in ip list. And there is no way to reset this view from this table. ![image](https://user-images.githubusercontent.com/13135279/167616702-1658a7f4-fb15-4311-8bd7-9c3c41128b85.png) Note: There is a work around suggested by `Simon T` to clear `table preferences ` for `IPAddressTable` in `/user/preferences/`. Which will return this table to default sorting with `X IPs available` positioned correctly.
adam added the type: bugstatus: accepted labels 2025-12-29 19:41:03 +01:00
adam closed this issue 2025-12-29 19:41:03 +01:00
adam commented 2025-12-29 19:41:04 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 11, 2022):

The fix here would seem to be to remove the available IP annotations entirely when ordering by an attribute other than IP address.

@jeremystretch commented on GitHub (May 11, 2022): The fix here would seem to be to remove the available IP annotations entirely when ordering by an attribute other than IP address.
adam commented 2025-12-29 19:41:04 +01:00
Author
Owner
Copy Link

@dreng commented on GitHub (May 12, 2022):

Another workaround would be to manually edit the URL and enter a value after "sort" that does not correspond to any column as stated here.

A simple fix could be to add a button or textlink pointing to /ipam/prefixes//ip-addresses/?sort=default. This could be adapted for any other section.

@dreng commented on GitHub (May 12, 2022): Another workaround would be to manually edit the URL and enter a value after "sort" that does not correspond to any column as stated [here](https://github.com/netbox-community/netbox/discussions/9295). A simple fix could be to add a button or textlink pointing to /ipam/prefixes/<id>/ip-addresses/?sort=default. This could be adapted for any other section.
adam commented 2025-12-29 19:41:04 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 12, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jul 12, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
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 status: accepted type: bug
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#6468
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?