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

Clone Saved Filters without function #7513

New Issue
Closed
opened 2025-12-29 20:24:32 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:24:32 +01:00
Owner
Copy Link

Originally created by @ShellBoyAFK on GitHub (Jan 13, 2023).

NetBox version

v3.4.2

Python version

3.10

Steps to Reproduce

  1. Click Other
  2. Click Saved Filters
  3. Click Add
  4. Fill the necessary fields with data
  5. Click Create
  6. Click on the New Saved Filter
  7. Click Clone
  8. See Nothing :

Expected Behavior

A clone function should clone something!
FMO I would have expected that I only have to fill in or change the name* and the slug*.

Observed Behavior

Originally created by @ShellBoyAFK on GitHub (Jan 13, 2023). ### NetBox version v3.4.2 ### Python version 3.10 ### Steps to Reproduce 1. Click Other 2. Click Saved Filters 3. Click Add 4. Fill the necessary fields with data 5. Click Create 6. Click on the New Saved Filter 7. Click Clone 8. See Nothing : ### Expected Behavior A clone function should clone something! FMO I would have expected that I only have to fill in or change the name* and the slug*. ### Observed Behavior -
adam closed this issue 2025-12-29 20:24:32 +01:00
adam commented 2025-12-29 20:24:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 20, 2023):

A clone function should clone something!

It does: The enabled and weight values are cloned. The name and slug are not, because these fields must be unique.

@jeremystretch commented on GitHub (Jan 20, 2023): > A clone function should clone something! It does: The `enabled` and `weight` values are cloned. The name and slug are not, because these fields must be unique.
adam commented 2025-12-29 20:24:33 +01:00
Author
Owner
Copy Link

@ShellBoyAFK commented on GitHub (Jan 26, 2023):

Hm! Not even that good ...

In my imagination (usability)! I imagine (as a pure work relief) that everything that is cloned is also copied. With Uniqen fields you can add a "_copy" or a "(1...)". Be creative.

The current "clone function" does not help me personally. The fields especially the Jinja2 must be adapted in my use case only slightly and Uniqe fields will adapt as a user of course itself.

Anyway, then keep it that way! I thought that was forgotten or the function does not apply here.

@ShellBoyAFK commented on GitHub (Jan 26, 2023): Hm! Not even that good ... In my imagination (usability)! I imagine (as a pure work relief) that everything that is cloned is also copied. With Uniqen fields you can add a "_copy" or a "(1...)". Be creative. The current "clone function" does not help me personally. The fields especially the Jinja2 must be adapted in my use case only slightly and Uniqe fields will adapt as a user of course itself. Anyway, then keep it that way! I thought that was forgotten or the function does not apply here.
adam commented 2025-12-29 20:24:33 +01:00
Author
Owner
Copy Link

@ShellBoyAFK commented on GitHub (Jan 26, 2023):

oh sorry i mean

  • Content types
  • Description
  • Parameters (JSON)
@ShellBoyAFK commented on GitHub (Jan 26, 2023): oh sorry i mean - Content types - Description - Parameters (JSON)
adam commented 2025-12-29 20:24:34 +01:00
Author
Owner
Copy Link

@FliesLikeABrick commented on GitHub (Mar 6, 2023):

@jeremystretch can you re-evaluate this bug report based on the last comment above, which was after closure ? Cloning a saved filter in the UI does not clone the content types, description, or parameters -- i.e. the substance of the saved filter. Or should a new bug report be opened for a cleaner history on the issue?

@FliesLikeABrick commented on GitHub (Mar 6, 2023): @jeremystretch can you re-evaluate this bug report based on the last comment above, which was after closure ? Cloning a saved filter in the UI does not clone the content types, description, or parameters -- i.e. the substance of the saved filter. Or should a new bug report be opened for a cleaner history on the issue?
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#7513
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?