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

Please add per-user favorites #3713

New Issue
Closed
opened 2025-12-29 18:30:44 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:30:44 +01:00
Owner
Copy Link

Originally created by @patrakov on GitHub (May 20, 2020).

Environment

  • Python version: 3.7.7
  • NetBox version: 2.7.11

Proposed Functionality

For each user, provide a way to star/unstar any objects that he has access to, and maybe also search queries. This starring should be specific for each user. Then, provide a quick way (e.g. a new menu link at the top) for the user to get a list of his starred objects, and in all searches, put them at the top if they match.

Use Case

I work mostly with the internal infrastructure VMs but also have access to customer VMs, so need quick access to the 172.31.100.0/24 prefix in order to be able to assign IPs but don't mind if I need to click a lot to get to routers and customer vlans. My colleague works with customers but also has access to the internal infrastructure, so he should be able to go to our routers, customers' vlans and so on (better ask him), but doesn't care if he needs to find the infrastructure VM network through all the menus.

We don't care about each others' favorite objects and don't even want to know that they exist, and definitely don't want to pollute the objects with tags meaningful only for a specific user.

Database Changes

Yes, we need to store personal favorite objects :)

External Dependencies

None.

Other information

I am aware of a closed feature request, #2640, which looks similar. However, the proposed "solution" with tags does not get the requirement that the favorites should be user-private.

Originally created by @patrakov on GitHub (May 20, 2020). ### Environment * Python version: 3.7.7 * NetBox version: 2.7.11 ### Proposed Functionality For each user, provide a way to star/unstar any objects that he has access to, and maybe also search queries. This starring should be specific for each user. Then, provide a quick way (e.g. a new menu link at the top) for the user to get a list of his starred objects, and in all searches, put them at the top if they match. ### Use Case I work mostly with the internal infrastructure VMs but also have access to customer VMs, so need quick access to the 172.31.100.0/24 prefix in order to be able to assign IPs but don't mind if I need to click a lot to get to routers and customer vlans. My colleague works with customers but also has access to the internal infrastructure, so he should be able to go to our routers, customers' vlans and so on (better ask him), but doesn't care if he needs to find the infrastructure VM network through all the menus. We don't care about each others' favorite objects and don't even want to know that they exist, and definitely don't want to pollute the objects with tags meaningful only for a specific user. ### Database Changes Yes, we need to store personal favorite objects :) ### External Dependencies None. ### Other information I am aware of a closed feature request, #2640, which looks similar. However, the proposed "solution" with tags does not get the requirement that the favorites should be user-private.
adam added the plugin candidate label 2025-12-29 18:30:44 +01:00
adam closed this issue 2025-12-29 18:30:44 +01:00
adam commented 2025-12-29 18:30:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 20, 2020):

Why not use browser bookmarks?

@jeremystretch commented on GitHub (May 20, 2020): Why not use browser bookmarks?
adam commented 2025-12-29 18:30:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 26, 2020):

I don't think this fits as a core feature, though it sounds like a good candidate for a plugin.

@jeremystretch commented on GitHub (May 26, 2020): I don't think this fits as a core feature, though it sounds like a good candidate for a plugin.
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 plugin candidate
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#3713
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?