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

Bulk editing should support setting all non-required fields to "none" #527

Closed
cdemi opened this issue Sep 1, 2016 · 6 comments
Closed

Bulk editing should support setting all non-required fields to "none" #527

cdemi opened this issue Sep 1, 2016 · 6 comments
Labels
type: feature Introduction of new functionality to the application

Comments

@cdemi
Copy link

cdemi commented Sep 1, 2016

In bulk edit, unchosen drop downs mean that the field is not to be edited. This makes it impossible to bulk edit a field to the default state
@frg
Copy link

frg commented Sep 6, 2016

Same here :/

@natashafenech
Copy link

Having the same issue +1

@jeremystretch jeremystretch added the type: feature Introduction of new functionality to the application label Sep 12, 2016
@jeremystretch
Copy link
Member

This is something I've been meaning to get to. v1.6 will include a "none" option for many fields, but eventually I'd like to add a separate "set to none" checkbox for every non-required field in every bulk edit form.

@frg
Copy link

frg commented Sep 12, 2016

Thanks for the update @jeremystretch. Any idea on release date of 1.6?

@jeremystretch
Copy link
Member

jeremystretch commented Sep 12, 2016 •
edited

@frg This week. Would have been earlier but I was away for a couple weeks.

@natashafenech
Copy link

Thanks. Sounds like a good solution!

@jeremystretch jeremystretch added this to the v1.7 milestone Sep 16, 2016
@jeremystretch jeremystretch changed the title When using bulk edit, it is not possible to bulk edit a dropdown item to the default NULL State Bulk editing should support setting all non-required fields to "none" Sep 16, 2016
@jeremystretch jeremystretch removed this from the v1.7 milestone Sep 16, 2016
jeremystretch added a commit that referenced this issue Sep 30, 2016
@jeremystretch
#527: Initial work to allow nullifying fields during bulk edit
3606606
if-fi pushed a commit to if-fi/netbox that referenced this issue Oct 1, 2016
@jeremystretch
netbox-community#527: Initial work to allow nullifying fields during …
64d5117 
…bulk edit
@jeremystretch jeremystretch mentioned this issue Oct 19, 2016
Merged
lampwins pushed a commit to lampwins/netbox that referenced this issue Oct 13, 2017
@jeremystretch
Fixes netbox-community#527: Support for nullifying custom fields duri…
f87a97f 
…ng bulk editing
@lock lock bot locked as resolved and limited conversation to collaborators Jan 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
type: feature Introduction of new functionality to the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@frg @cdemi @natashafenech @jeremystretch