&#34;add new&#34; option for dropdown menus #365

@anthraxau commented on GitHub (Aug 19, 2016):

ive fallen victim to this a few times

@anthraxau commented on GitHub (Aug 19, 2016): ive fallen victim to this a few times

adam commented

@aoyawale commented on GitHub (Aug 25, 2016):

I have to agree. 1+

@aoyawale commented on GitHub (Aug 25, 2016): I have to agree. 1+

adam commented

@mryauch commented on GitHub (Oct 25, 2016):

+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.

@mryauch commented on GitHub (Oct 25, 2016): +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.

adam commented

@jeremystretch commented on GitHub (Mar 23, 2017):

This is something we should be able to support starting with v2.0, which introduces full write API support.

@jeremystretch commented on GitHub (Mar 23, 2017): This is something we should be able to support starting with v2.0, which introduces full write API support.

adam commented

@alexjhart commented on GitHub (May 11, 2017):

Good to hear, especially with the release of v2.0 :)

@alexjhart commented on GitHub (May 11, 2017): Good to hear, especially with the release of v2.0 :)

adam commented

@tyler-8 commented on GitHub (Aug 5, 2019):

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).

@tyler-8 commented on GitHub (Aug 5, 2019): 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).

adam commented

@alexjhart commented on GitHub (Aug 6, 2019):

Yes, it is still necessary. The workflow is still improved when you can create items that are missing without leaving the page/tab.

@alexjhart commented on GitHub (Aug 6, 2019): Yes, it is still necessary. The workflow is still improved when you can create items that are missing without leaving the page/tab.

adam commented

@DanSheps commented on GitHub (Sep 25, 2019):

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

@DanSheps commented on GitHub (Sep 25, 2019): 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

adam commented

@jeremystretch commented on GitHub (Jul 24, 2020):

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.

@jeremystretch commented on GitHub (Jul 24, 2020): 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.

adam commented

@stale[bot] commented on GitHub (Sep 7, 2020):

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.

@stale[bot] commented on GitHub (Sep 7, 2020): 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](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).

adam commented

@stale[bot] commented on GitHub (Sep 23, 2020):

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.

@stale[bot] commented on GitHub (Sep 23, 2020): 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.

adam commented

@jeremystretch commented on GitHub (Dec 18, 2021):

With the recent introduction of HTMX (see #8057), I think this is now a real possibility. More investigation is needed to see what's feasible but I'm confident we can come up with something.

@jeremystretch commented on GitHub (Dec 18, 2021): With the recent introduction of HTMX (see #8057), I think this is now a real possibility. More investigation is needed to see what's feasible but I'm confident we can come up with something.

adam commented