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

Contact Assignment Priority is Required in API, not in GUI #6455

New Issue
Closed
opened 2025-12-29 19:40:54 +01:00 by adam · 0 comments
adam commented 2025-12-29 19:40:54 +01:00
Owner
Copy Link

Originally created by @tyler-8 on GitHub (May 6, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.2.2

Python version

3.9

Steps to Reproduce

  1. Create a Site
  2. Create a Contact Role, "Main Phone"
  3. Create a Contact with name, phone fields filled out
  4. Using the /tenancy/contact-assignments/ API, perform a POST operation to create a new assignment using the site, contact, and role in previous steps, but don't add the priority field.

Expected Behavior

HTTP 201 with the Contact Assignment being created successfully, and null as the Priority field value.

Not all Contacts are going to have or require a "priority" so it makes sense to have this as an optional field. In the GUI, the Priority field is optional and displays a - as I would expect when that field is blank.

Observed Behavior

HTTP 400

{'priority': ['This field is required.']}

Originally created by @tyler-8 on GitHub (May 6, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.2.2 ### Python version 3.9 ### Steps to Reproduce 1. Create a Site 2. Create a Contact Role, "Main Phone" 3. Create a Contact with name, phone fields filled out 4. Using the `/tenancy/contact-assignments/` API, perform a POST operation to create a new assignment using the site, contact, and role in previous steps, but don't add the `priority` field. ### Expected Behavior HTTP 201 with the Contact Assignment being created successfully, and `null` as the Priority field value. Not all Contacts are going to have or require a "priority" so it makes sense to have this as an optional field. In the GUI, the Priority field is optional and displays a `-` as I would expect when that field is blank. ### Observed Behavior HTTP 400 `{'priority': ['This field is required.']}`
adam added the type: bugstatus: accepted labels 2025-12-29 19:40:54 +01:00
adam closed this issue 2025-12-29 19:40:54 +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: 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#6455
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?