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.

Sign up for GitHub

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

Jump to bottom

Visual bug. After edited or deleted custom field, bulk create and edit will keep the custom field in display field (not attribute) #6817

Closed
jk-onnet opened this issue Jul 27, 2021 · 2 comments
Closed

Visual bug. After edited or deleted custom field, bulk create and edit will keep the custom field in display field (not attribute) #6817

jk-onnet opened this issue Jul 27, 2021 · 2 comments
Assignees
@jeremystretch
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@jk-onnet
Copy link

NetBox version

v2.11.7 (tested on demo instance too)

Python version

3.9

Steps to Reproduce

  1. Add custom field "vmid" in virtualization (admin)
  2. Edit custom field "vmid" name in virtualization (admin)
  3. Add custom field "core" name in virtualization (admin)
  4. Delete custom field "core" name in virtualization (admin)
  5. Bulk edit or delete in virtualization page

Expected Behavior

image

Observed Behavior

image
@jk-onnet jk-onnet added the type: bug A confirmed report of unexpected behavior in the application label Jul 27, 2021
@jeremystretch jeremystretch added the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label Jul 27, 2021
@jeremystretch
Copy link
Member

For clarification of the reproduction instructions, the user needs to add the custom fields under the object table configuration for them to appear.

@jeremystretch jeremystretch mentioned this issue Sep 28, 2021
Closed
@opericgithub
Copy link

#7310 might be similar to this, but not quite same. anyway, i hope this issue will be resolved sometime soon.

@jeremystretch jeremystretch mentioned this issue Oct 1, 2021
Closed
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Oct 2, 2021
@jeremystretch jeremystretch self-assigned this Oct 2, 2021
@jeremystretch jeremystretch mentioned this issue Oct 4, 2021
Merged
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 31, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremystretch jeremystretch

Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jeremystretch @opericgithub @jk-onnet