Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom Fields after block Comments #16807

Closed
dnk2009-1 opened this issue Jul 3, 2024 · 0 comments
Closed

Custom Fields after block Comments #16807

dnk2009-1 opened this issue Jul 3, 2024 · 0 comments
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@dnk2009-1
Copy link

dnk2009-1 commented Jul 3, 2024

Deployment Type

Self-hosted

NetBox Version

v4.0.6 demo

Python Version

3.10

Steps to Reproduce

  1. add Custom Field "DSW", choise OBJECT TYPES Prefix and VLAN.
  2. in IPAM Prefixes, all good. Custom field "DSW" located before block Comments
    3 in IPAM Vlans, not good. Custom field "DSW" located after block Comments
    prefixes
    vlans
    custom field

Expected Behavior

in IPAM Vlans, Custom field "DSW" located after block Comments

Observed Behavior

in IPAM Vlans, not good. Custom field "DSW" located after block Comments

@dnk2009-1 dnk2009-1 added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Jul 3, 2024
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels Jul 3, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants