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

Tags not available through REST API on Wireless LAN #5821

New Issue
Closed
opened 2025-12-29 19:33:11 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:33:11 +01:00
Owner
Copy Link

Originally created by @rodvand on GitHub (Dec 21, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.1.2

Python version

3.8

Steps to Reproduce

Through the Web interface:

  1. Create tag "TagA"
  2. Create a Wireless LAN "WLAN One" and add the tag "TagA" to the Wireless LAN

Expected Behavior

To see the tags assigned to the Wireless LAN in the API browser.

Observed Behavior

The tag is not visible through the API. It is also not assign tags using the REST API. It is visible in the Web UI.

Originally created by @rodvand on GitHub (Dec 21, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.1.2 ### Python version 3.8 ### Steps to Reproduce Through the Web interface: 1. Create tag "TagA" 2. Create a Wireless LAN "WLAN One" and add the tag "TagA" to the Wireless LAN ### Expected Behavior To see the tags assigned to the Wireless LAN in the API browser. ### Observed Behavior The tag is not visible through the API. It is also not assign tags using the REST API. It is visible in the Web UI.
adam added the type: bugstatus: accepted labels 2025-12-29 19:33:11 +01:00
adam closed this issue 2025-12-29 19:33:11 +01:00
adam commented 2025-12-29 19:33:11 +01:00
Author
Owner
Copy Link

@rodvand commented on GitHub (Dec 21, 2021):

It's the same with the Wireless Link model. Can see the tags in the Web UI, but not create/see with the REST API.

@rodvand commented on GitHub (Dec 21, 2021): It's the same with the Wireless Link model. Can see the tags in the Web UI, but not create/see with the REST API.
adam commented 2025-12-29 19:33:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 22, 2021):

Some other fields seem to have been omitted from the serializers as well. It actually looks like an entire line within the fields attribute on either serializer was mistakenly deleted at some point.

@jeremystretch commented on GitHub (Dec 22, 2021): Some other fields seem to have been omitted from the serializers as well. It actually looks like an entire line within the `fields` attribute on either serializer was mistakenly deleted at some point.
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: bug
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#5821
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?