Consider you are adding a new device (this applies to other contexts as well, but I'm using device as an example). One will need to set the role, manufacture, type, etc. If you don't have all of those things pre-created, you end up getting forced to fill out the form again after leaving the page to create them. Wouldn't you rather have a way to add those things on the fly so you can just continue setting up the device without the extra headache? If an "add new" option was available at the top of the list or a plus sign next to the dropdown, you could click that to get a modal box style pop up to create the missing option which triggers a dropdown list refresh on save.
ive fallen victim to this a few times
I have to agree. 1+
+1 This has definitely been one of my biggest issues with having just set up the system and manually adding items while a newbie. As it is now it's pretty much assuming you know everything that will be a required field ahead of time and have already set it up.
This is something we should be able to support starting with v2.0, which introduces full write API support.
Good to hear, especially with the release of v2.0 :)
With the Select2 dropdown fields is this necessary anymore? Re-selecting the dropdown triggers a new API call which will pick up any newly created entries (in another tab for example).
Yes, it is still necessary. The workflow is still improved when you can create items that are missing without leaving the page/tab.
Just to save this for future: https://stackoverflow.com/questions/38635800/i-need-to-add-add-new-item-option-in-select2/38655413
Various different approaches to "create new" in Select2
The development burden for implementing this using the current UI is likely disproportionate to the value gained. Leaving this open for anyone who wants to volunteer. Otherwise, it will be reconsidered during a future overhaul of the UI.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.
This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Most helpful comment
This is something we should be able to support starting with v2.0, which introduces full write API support.