starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Make a printer friendly layout of all racks for auditing. #123

New Issue
Closed
opened 2025-12-29 15:33:56 +01:00 by adam · 14 comments
adam commented 2025-12-29 15:33:56 +01:00
Owner
Copy Link

Originally created by @Luc1f3rUK on GitHub (Jul 1, 2016).

I think it would be amazing to have a nice printout of the rack plans. Mainly for auditing (And keeping the bosses happy)

Something like, 4 racks to a page, with U Numbers, server names etc.

Thanks!

Originally created by @Luc1f3rUK on GitHub (Jul 1, 2016). I think it would be amazing to have a nice printout of the rack plans. Mainly for auditing (And keeping the bosses happy) Something like, 4 racks to a page, with U Numbers, server names etc. Thanks!
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 15:33:56 +01:00
adam closed this issue 2025-12-29 15:33:57 +01:00
adam commented 2025-12-29 15:33:58 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jul 1, 2016):

I would suggest a rack per-page for readability and to give room for notes or anything else - especially if you are printing to A4

@bellwood commented on GitHub (Jul 1, 2016): I would suggest a rack per-page for readability and to give room for notes or anything else - especially if you are printing to A4
adam commented 2025-12-29 15:33:58 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jul 20, 2016):

@RyanMonkey just a follow up - would this be something you'd like at the rack group level or site level or installation level, etc.

@bellwood commented on GitHub (Jul 20, 2016): @RyanMonkey just a follow up - would this be something you'd like at the rack group level or site level or installation level, etc.
adam commented 2025-12-29 15:33:58 +01:00
Author
Owner
Copy Link

@Luc1f3rUK commented on GitHub (Jul 24, 2016):

@bellwood I think a site level and individual rack level would be great!

@Luc1f3rUK commented on GitHub (Jul 24, 2016): @bellwood I think a site level and individual rack level would be great!
adam commented 2025-12-29 15:33:59 +01:00
Author
Owner
Copy Link

@jscobbie73 commented on GitHub (Sep 19, 2017):

Any update on this request? Certainly something I am looking forward to as well.

@jscobbie73 commented on GitHub (Sep 19, 2017): Any update on this request? Certainly something I am looking forward to as well.
adam commented 2025-12-29 15:33:59 +01:00
Author
Owner
Copy Link

@harsh-kotak commented on GitHub (Jan 5, 2018):

Any update or timeline on this request? The lack of a feature to export/print Rack elevations is making us maintain additional spreadsheets to send out to lab technicians. The print view could be at rack group level with Name and Device Type displayed in elevations.

@harsh-kotak commented on GitHub (Jan 5, 2018): Any update or timeline on this request? The lack of a feature to export/print Rack elevations is making us maintain additional spreadsheets to send out to lab technicians. The print view could be at rack group level with Name and Device Type displayed in elevations.
adam commented 2025-12-29 15:34:00 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Mar 30, 2018):

I would love a feature like this. Here are the two parts I would love to see:

  1. Printer Friendly export of layout from the Rack Page (Single Rack, Front and Back)
  2. Printer Friendly export of layout from the Rack Group Page (Multiple Racks, 2-4 per page, Front or Back only, Configurable)
  3. Printer Friendly export of layout from the Site Page (Multiple Racks, 2-4 per page, Front or Back only, Configurable)

I might actually give this a wack if Jeremy doesn't mind. I have never coded Python but I imagine a view is rather easy.

@DanSheps commented on GitHub (Mar 30, 2018): I would love a feature like this. Here are the two parts I would love to see: 1. Printer Friendly export of layout from the Rack Page (Single Rack, Front and Back) 2. Printer Friendly export of layout from the Rack Group Page (Multiple Racks, 2-4 per page, Front or Back only, Configurable) 3. Printer Friendly export of layout from the Site Page (Multiple Racks, 2-4 per page, Front or Back only, Configurable) I might actually give this a wack if Jeremy doesn't mind. I have never coded Python but I imagine a view is rather easy.
adam commented 2025-12-29 15:34:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 2, 2018):

Blocked by #2248

@jeremystretch commented on GitHub (Aug 2, 2018): Blocked by #2248
adam commented 2025-12-29 15:34:01 +01:00
Author
Owner
Copy Link

@jameswhite4684 commented on GitHub (Mar 5, 2019):

A printer friendly view would be great, like excluding search bar and navigation links.

@jameswhite4684 commented on GitHub (Mar 5, 2019): A printer friendly view would be great, like excluding search bar and navigation links.
adam commented 2025-12-29 15:34:01 +01:00
Author
Owner
Copy Link

@em-winterschon commented on GitHub (May 20, 2019):

Exporting rack elevation data to CSV would be very useful, in addition to the printing support already mentioned. There's a CSV export function for rack list, but not for elevation data (serial numbers, hostname, location, etc).

@em-winterschon commented on GitHub (May 20, 2019): Exporting rack elevation data to CSV would be very useful, in addition to the printing support already mentioned. There's a CSV export function for rack list, but not for elevation data (serial numbers, hostname, location, etc).
adam commented 2025-12-29 15:34:02 +01:00
Author
Owner
Copy Link

@jameswhite4684 commented on GitHub (Jun 6, 2019):

Rack Elevations / Group View view printing displays scrollbar and white space where search bar would be, thus distorting the print job.

Rack.Elevations.-.NetBox.pdf

@jameswhite4684 commented on GitHub (Jun 6, 2019): Rack Elevations / Group View view printing displays scrollbar and white space where search bar would be, thus distorting the print job. [Rack.Elevations.-.NetBox.pdf](https://github.com/digitalocean/netbox/files/3262945/Rack.Elevations.-.NetBox.pdf)
adam commented 2025-12-29 15:34:02 +01:00
Author
Owner
Copy Link

@rbenigno commented on GitHub (Jan 9, 2020):

Looks like the blockers for this have been closed?

@rbenigno commented on GitHub (Jan 9, 2020): Looks like the blockers for this have been closed?
adam commented 2025-12-29 15:34:03 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 17, 2020):

Looking for volunteers to take on this work. It should be fairly straightforward given that rack elevations are now rendered as SVG images.

@jeremystretch commented on GitHub (Dec 17, 2020): Looking for volunteers to take on this work. It should be fairly straightforward given that rack elevations are now rendered as SVG images.
adam commented 2025-12-29 15:34:03 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Feb 2, 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.

@stale[bot] commented on GitHub (Feb 2, 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 15:34:04 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Feb 18, 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.

@stale[bot] commented on GitHub (Feb 18, 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 status: needs owner 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#123
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?