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

Add the option to select the "Region" column in the Racks view #4808

New Issue
Closed
opened 2025-12-29 19:20:50 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:20:50 +01:00
Owner
Copy Link

Originally created by @Andreich2010 on GitHub (Apr 22, 2021).

NetBox version

v2.10.4

Feature type

Data model extension

Proposed functionality

In the Racks view (Host: 8000 / DCIM / Racks /), the "Region" field we use as a "company name", and we use the "SITES" field as "building".
In some enterprises, the identical marking of rack is found. Therefore, we want to request the functionality that displays the "Region" field in the "Rack tab" table view

Use case

In our organization, more than 25 regions, in some names "Site" the same. When searching for the desired "SITE", the employee does not have to resort to the use of the search filter, which will significantly reduce the time for operational activities.

Database changes

Probably a simple solution will be a binding "ID Region" in the "DICM_RACK" table.
Or class changes in Racktable (\ OPT \ Netbox \ Netbox \ dcim \ tables \ racks.py) by connecting the desired "ID Region" through Queryset

External dependencies

No dependencies

Originally created by @Andreich2010 on GitHub (Apr 22, 2021). ### NetBox version v2.10.4 ### Feature type Data model extension ### Proposed functionality In the Racks view (Host: 8000 / DCIM / Racks /), the "Region" field we use as a "company name", and we use the "SITES" field as "building". In some enterprises, the identical marking of rack is found. Therefore, we want to request the functionality that displays the "Region" field in the "Rack tab" table view ### Use case In our organization, more than 25 regions, in some names "Site" the same. When searching for the desired "SITE", the employee does not have to resort to the use of the search filter, which will significantly reduce the time for operational activities. ### Database changes Probably a simple solution will be a binding "ID Region" in the "DICM_RACK" table. Or class changes in Racktable (\ OPT \ Netbox \ Netbox \ dcim \ tables \ racks.py) by connecting the desired "ID Region" through Queryset ### External dependencies No dependencies
adam added the type: featurepending closure labels 2025-12-29 19:20:50 +01:00
adam closed this issue 2025-12-29 19:20:50 +01:00
adam commented 2025-12-29 19:20:51 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 22, 2021):

In the Racks view (Host: 8000 / DCIM / Racks /), the "Region" field we use as a "company name", and we use the "SITES" field as "building".

Tenancy assignment would be more appropriate for this, as regions are intended to convey geographic location.

@jeremystretch commented on GitHub (Apr 22, 2021): > In the Racks view (Host: 8000 / DCIM / Racks /), the "Region" field we use as a "company name", and we use the "SITES" field as "building". Tenancy assignment would be more appropriate for this, as regions are intended to convey geographic location.
adam commented 2025-12-29 19:20:51 +01:00
Author
Owner
Copy Link

@Andreich2010 commented on GitHub (Apr 22, 2021):

Yes, it is good, but we use the field "Tenancy" as a "responsible" and "group responsible", it approached us more.

@Andreich2010 commented on GitHub (Apr 22, 2021): Yes, it is good, but we use the field "Tenancy" as a "responsible" and "group responsible", it approached us more.
adam commented 2025-12-29 19:20:51 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 22, 2021):

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. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jun 22, 2021): 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. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:20:52 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 23, 2021):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jul 23, 2021): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure 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#4808
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?