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 support for delegating rack/patching request #7200

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

Originally created by @kifeo on GitHub (Nov 4, 2022).

NetBox version

v3.3.7

Feature type

New functionality

Proposed functionality

add support for requesting a new / change / removal of racking of a device or patching cables from devies to another team.

Use case

Now that remote work is getting more and more accepted, this would add the possibility to the product to add the request to another team to handle the datacenter physical management.

This would also allow a single team be able to handle the workflow of handling the racking and patching.

Database changes

No response

External dependencies

No response

Originally created by @kifeo on GitHub (Nov 4, 2022). ### NetBox version v3.3.7 ### Feature type New functionality ### Proposed functionality add support for requesting a new / change / removal of racking of a device or patching cables from devies to another team. ### Use case Now that remote work is getting more and more accepted, this would add the possibility to the product to add the request to another team to handle the datacenter physical management. This would also allow a single team be able to handle the workflow of handling the racking and patching. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featureplugin candidate labels 2025-12-29 20:20:22 +01:00
adam closed this issue 2025-12-29 20:20:22 +01:00
adam commented 2025-12-29 20:20:23 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 16, 2022):

Implementing a change control process is out of scope for NetBox core, but could work very well as a plugin.

@jeremystretch commented on GitHub (Nov 16, 2022): Implementing a change control process is out of scope for NetBox core, but could work very well as a plugin.
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 plugin candidate 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#7200
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?