starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Feature Request - Assign Services to Devices #465

New Issue
Closed
opened 2025-12-29 16:22:25 +01:00 by adam · 8 comments
adam commented 2025-12-29 16:22:25 +01:00
Owner
Copy Link

Originally created by @pettcomputers on GitHub (Oct 4, 2016).

In our organization, we would like to be able to assign multiple services to devices and tenants in Netbox so that we can quickly identify all devices related to a particular service/product we offer.

I was thinking this could be accomplished two different ways, what are your thoughts?

  1. Add a new service category within the application that lists services, then attach the services to each device that the service relies on, or
  2. Add a listbox custom field that allows multiple selections so we can add a custom field to each device that allows us to select one or more services that rely on the device like the screenshot attached.

selections

Originally created by @pettcomputers on GitHub (Oct 4, 2016). In our organization, we would like to be able to assign multiple services to devices and tenants in Netbox so that we can quickly identify all devices related to a particular service/product we offer. I was thinking this could be accomplished two different ways, what are your thoughts? 1. Add a new service category within the application that lists services, then attach the services to each device that the service relies on, or 2. Add a listbox custom field that allows multiple selections so we can add a custom field to each device that allows us to select one or more services that rely on the device like the screenshot attached. ![selections](https://cloud.githubusercontent.com/assets/20682729/19080623/41179b22-8a1d-11e6-8054-f7351513ea01.png)
adam closed this issue 2025-12-29 16:22:25 +01:00
adam commented 2025-12-29 16:22:26 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 4, 2016):

This sounds like a good use case for custom fields. The concept of a "service" is going to vary drastically among organizations.

@jeremystretch commented on GitHub (Oct 4, 2016): This sounds like a good use case for custom fields. The concept of a "service" is going to vary drastically among organizations.
adam commented 2025-12-29 16:22:26 +01:00
Author
Owner
Copy Link

@pettcomputers commented on GitHub (Oct 4, 2016):

Is there a way to possibly add a custom field that allows multiple selections like in the screen shot?

@pettcomputers commented on GitHub (Oct 4, 2016): Is there a way to possibly add a custom field that allows multiple selections like in the screen shot?
adam commented 2025-12-29 16:22:26 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 4, 2016):

Unfortunately, no: custom selection fields are single value only. Sorry, but we can't extend NetBox to fit every need.

@jeremystretch commented on GitHub (Oct 4, 2016): Unfortunately, no: custom selection fields are single value only. Sorry, but we can't extend NetBox to fit every need.
adam commented 2025-12-29 16:22:26 +01:00
Author
Owner
Copy Link

@pettcomputers commented on GitHub (Oct 4, 2016):

No worries, I understand.

On Oct 4, 2016 2:11 PM, "Jeremy Stretch" notifications@github.com wrote:

Unfortunately, no: custom selection fields are single value only. Sorry,
but we can't extend NetBox to fit every need.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/digitalocean/netbox/issues/597#issuecomment-251483846,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATuX6S1P9oY8lfPOtNdXnp7xMfKBMA72ks5qwqTogaJpZM4KN0yR
.

@pettcomputers commented on GitHub (Oct 4, 2016): No worries, I understand. On Oct 4, 2016 2:11 PM, "Jeremy Stretch" notifications@github.com wrote: > Unfortunately, no: custom selection fields are single value only. Sorry, > but we can't extend NetBox to fit every need. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > https://github.com/digitalocean/netbox/issues/597#issuecomment-251483846, > or mute the thread > https://github.com/notifications/unsubscribe-auth/ATuX6S1P9oY8lfPOtNdXnp7xMfKBMA72ks5qwqTogaJpZM4KN0yR > .
adam commented 2025-12-29 16:22:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 4, 2016):

I'll leave this open for a while to see if there's any other interest in something like this, just in case.

@jeremystretch commented on GitHub (Oct 4, 2016): I'll leave this open for a while to see if there's any other interest in something like this, just in case.
adam commented 2025-12-29 16:22:27 +01:00
Author
Owner
Copy Link

@pettcomputers commented on GitHub (Oct 4, 2016):

Thanks!

On Tue, Oct 4, 2016 at 2:23 PM, Jeremy Stretch notifications@github.com
wrote:

I'll leave this open for a while to see if there's any other interest in
something like this, just in case.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/digitalocean/netbox/issues/597#issuecomment-251486799,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATuX6bn4cs8-K080HlKPhkxTzT-8Fk1Iks5qwqe1gaJpZM4KN0yR
.

@pettcomputers commented on GitHub (Oct 4, 2016): Thanks! On Tue, Oct 4, 2016 at 2:23 PM, Jeremy Stretch notifications@github.com wrote: > I'll leave this open for a while to see if there's any other interest in > something like this, just in case. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > https://github.com/digitalocean/netbox/issues/597#issuecomment-251486799, > or mute the thread > https://github.com/notifications/unsubscribe-auth/ATuX6bn4cs8-K080HlKPhkxTzT-8Fk1Iks5qwqe1gaJpZM4KN0yR > .
adam commented 2025-12-29 16:22:27 +01:00
Author
Owner
Copy Link

@askbow commented on GitHub (Nov 11, 2016):

Won't this need be (at least partly) addressed by #132 ?

@askbow commented on GitHub (Nov 11, 2016): Won't this need be (at least partly) addressed by #132 ?
adam commented 2025-12-29 16:22:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 22, 2016):

True, #132 will probably be sufficient to address this.

@jeremystretch commented on GitHub (Nov 22, 2016): True, #132 will probably be sufficient to address this.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#465
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?