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

Image Attachments section redesign #10565

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

Originally created by @artiomello on GitHub (Dec 11, 2024).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v4.1.6

Feature type

Change to existing functionality

Triage priority

N/A

Proposed functionality

I believe the Image Attachment section needs to be revised to have it reflect data a bit more concisely, and precisely at that.

  1. Image size
    image

Size needs to be shown in MB, not in bytes. I'm almost 40 now and even I can't recall a single time in my life where image size in bytes would make any sense to me. Let alone now.

  1. Name and Image columns
    image

I think only one of them actually needs to stay. If you give a name to an image during upload - it's renamed accordingly, and the new name displayed in both columns. If you don't give a name, then the file name is taken and is displayed only in the Image column.

You can't have a situation where these two properties would be different, rather (and weirdly enough) omitted in some cases. So, they're pretty much the same. Hence having both of them doesn't make much sense.

  1. Referencing image attachments in other objects and views

So, if we open any object that has image attachments like this one, that has two:
image

We see that it likely filters that same original image table with itself, and we get the same columns as in the original table:
image
Only here this information is completely redundant:

  • We already know its name and that it's a site. Showing these properties here would make sense only in case it would show images for the site's child objects (which it should definitely not).
  • The image/name pair is redundant, as described above.
  • The size in bytes looks more like a phone number than anything else.
  • All in all, this redundant information just adds more clutter to the object's page.

What really should be displayed here are:

  • Name (serving as a pop-up image window).
  • Size (in MB, obviously).
  • Creation timestamp.

Use case

Updating this table, its object properties and how they are presented in other views/objects would make certain netbox pages less cluttery and more concise, showing only that which has value. This is especially true when viewing some more data rich objects, such as sites and racks.

Less is more, as they say.

Database changes

No response

External dependencies

No response

Originally created by @artiomello on GitHub (Dec 11, 2024). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v4.1.6 ### Feature type Change to existing functionality ### Triage priority N/A ### Proposed functionality I believe the `Image Attachment` section needs to be revised to have it reflect data a bit more concisely, and precisely at that. 1. Image size <img width="1061" alt="image" src="https://github.com/user-attachments/assets/c8708aba-5a0e-4e12-bef0-db7b5190355d"> Size needs to be shown in MB, not in bytes. I'm almost 40 now and even I can't recall a single time in my life where image size in bytes would make any sense to me. Let alone now. --- 2. Name and Image columns <img width="412" alt="image" src="https://github.com/user-attachments/assets/60f768f9-1fe2-466b-97cf-a269ec8e3949"> I think only one of them actually needs to stay. If you give a name to an image during upload - it's renamed accordingly, and the new name displayed in both columns. If you don't give a name, then the file name is taken and is displayed only in the `Image` column. You can't have a situation where these two properties would be different, rather (and weirdly enough) omitted in some cases. So, they're pretty much the same. Hence having both of them doesn't make much sense. --- 3. Referencing image attachments in other objects and views So, if we open any object that has image attachments like this one, that has two: <img width="1053" alt="image" src="https://github.com/user-attachments/assets/0dd5088a-a49c-4fa6-b858-b0f2a1ed5d25"> We see that it likely filters that same original image table with itself, and we get the same columns as in the original table: <img width="583" alt="image" src="https://github.com/user-attachments/assets/b5b68cba-9f48-4aa8-8b0f-c7a0c1e1523b"> Only here this information is completely redundant: - We already know its name and that it's a site. Showing these properties here would make sense only in case it would show images for the site's child objects (which it should definitely not). - The image/name pair is redundant, as described above. - The size in bytes looks more like a phone number than anything else. - All in all, this redundant information just adds more clutter to the object's page. What really should be displayed here are: - Name (serving as a pop-up image window). - Size (in MB, obviously). - Creation timestamp. ### Use case Updating this table, its object properties and how they are presented in other views/objects would make certain netbox pages less cluttery and more concise, showing only that which has value. This is especially true when viewing some more data rich objects, such as sites and racks. Less is more, as they say. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:33:12 +01:00
adam closed this issue 2025-12-29 21:33:12 +01:00
adam commented 2025-12-29 21:33:13 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 17, 2025):

Blocked by #18990

@jeremystretch commented on GitHub (Jul 17, 2025): Blocked by #18990
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 complexity: low status: accepted 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#10565
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?