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

Clarify screen layouts for VLAN tags versus labelling tags #2388

New Issue
Closed
opened 2025-12-29 17:25:36 +01:00 by adam · 0 comments
adam commented 2025-12-29 17:25:36 +01:00
Owner
Copy Link

Originally created by @candlerb on GitHub (Feb 15, 2019).

Environment

  • Python version: 3.5.2
  • NetBox version: 2.5.6

Proposed Functionality

When you create an interface and/or first set its 802.1Q mode, you currently see this:

image

IMO this is confusing, since the "Tags" here don't refer to VLAN tags. It's only after you've saved the interface that you then get the table underneath for "802.1Q VLANs".

I suggest moving "Tags" higher up the screen; and/or including the 802.1Q VLANs table always, even when the 802.1Q mode hasn't been set (it can be greyed out).

Use Case

New user adding / updating interfaces and trying to associate VLANs / VLAN tags.

Database Changes

None

External Dependencies

None

Originally created by @candlerb on GitHub (Feb 15, 2019). ### Environment * Python version: 3.5.2 * NetBox version: 2.5.6 ### Proposed Functionality When you create an interface and/or first set its 802.1Q mode, you currently see this: ![image](https://user-images.githubusercontent.com/44789/52852178-c6bc2400-310f-11e9-857f-ddeadd4516bb.png) IMO this is confusing, since the "Tags" here don't refer to VLAN tags. It's only after you've saved the interface that you then get the table underneath for "802.1Q VLANs". I suggest moving "Tags" higher up the screen; and/or including the 802.1Q VLANs table always, even when the 802.1Q mode hasn't been set (it can be greyed out). ### Use Case New user adding / updating interfaces and trying to associate VLANs / VLAN tags. ### Database Changes None ### External Dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 17:25:36 +01:00
adam closed this issue 2025-12-29 17:25:36 +01:00
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 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#2388
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?