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

Planned Devices and Rack Reservations webui adjustments #3716

New Issue
Closed
opened 2025-12-29 18:30:44 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:30:44 +01:00
Owner
Copy Link

Originally created by @ryanmerolle on GitHub (May 21, 2020).

Environment

  • Python version: 3.6.9
  • NetBox version: 2.8.4

Proposed Functionality

It would be useful for planned devices to be indicated as such in the rack elevations view. There are several ways to achieve this, and I think the easiest most compliant with the netbox philosophy should be taken. I am not prescribing a way to do it, but possible approaches could be:

  • Show these planned status devices just like rack reservations because they are one in the same, just a reservation with more details and a status to track the lifecycle
  • Tool tip update next to the item in the rack view
  • Some sort of other visual representation of the status being planned with dotted instead of solid lines for the shape, a faded background color, or different font style. All of these items may be challenging to apply to devices with an image associated to the device type.
  • Something else I am not thinking of

Use Case

Ability to understand what is truly "reserved" ie including planned devices.

Database Changes

I think this should be minimal since I am proposing a webui tweak.

External Dependencies

N/A

Originally created by @ryanmerolle on GitHub (May 21, 2020). ### Environment * Python version: 3.6.9 * NetBox version: 2.8.4 ### Proposed Functionality It would be useful for planned devices to be indicated as such in the rack elevations view. There are several ways to achieve this, and I think the easiest most compliant with the netbox philosophy should be taken. I am not prescribing a way to do it, but possible approaches could be: - Show these planned status devices just like rack reservations because they are one in the same, just a reservation with more details and a status to track the lifecycle - Tool tip update next to the item in the rack view - Some sort of other visual representation of the status being planned with dotted instead of solid lines for the shape, a faded background color, or different font style. All of these items may be challenging to apply to devices with an image associated to the device type. - Something else I am not thinking of ### Use Case Ability to understand what is truly "reserved" ie including planned devices. ### Database Changes I think this should be minimal since I am proposing a webui tweak. ### External Dependencies N/A
adam added the pending closure label 2025-12-29 18:30:44 +01:00
adam closed this issue 2025-12-29 18:30:45 +01:00
adam commented 2025-12-29 18:30:45 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jun 4, 2020):

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.

@stale[bot] commented on GitHub (Jun 4, 2020): 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 18:30:45 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jun 11, 2020):

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.

@stale[bot] commented on GitHub (Jun 11, 2020): 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
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#3716
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?