Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export current view of IP Addresses #14567

Open
mburgholte opened this issue Dec 20, 2023 · 6 comments · May be fixed by #15659
Open

Export current view of IP Addresses #14567

mburgholte opened this issue Dec 20, 2023 · 6 comments · May be fixed by #15659
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@mburgholte
Copy link

Deployment Type

Self-hosted

NetBox Version

v3.6.7

Python Version

3.8

Steps to Reproduce

Tested with demo.netbox.dev

  1. Select IPAM -> IP Addresses (on the top Results shows 183)
    image
  2. Quick search 172.16 (Results stays on 183)
    image
  3. Export Current view
    image

Expected Behavior

Shouldn't it be the case that when filtering by addresses, the number of results is reduced and accordingly the export of the current view only contains the filtered addresses?

Observed Behavior

When exporting, all addresses are always exported.

@mburgholte mburgholte added the type: bug A confirmed report of unexpected behavior in the application label Dec 20, 2023
@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: low Does not significantly disrupt application functionality, or a workaround is available labels Dec 20, 2023
@jsenecal
Copy link
Contributor

@jeremystretch I could work on that one, I have a good idea how to fix this.

@abhi1693 abhi1693 added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Dec 20, 2023
@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation and removed status: accepted This issue has been accepted for implementation labels Mar 9, 2024
@arthanson
Copy link
Collaborator

@jsenecal do you still want to pick this one up?

@jsenecal
Copy link
Contributor

jsenecal commented Apr 3, 2024

Hey @arthanson, sorry nobody msgd me when I got it assigned to me and I did not notice nor specifically looked for issues assigned to me.

I'm not familiar with the new v4 codebase yet however so it may take some time.

@jeremystretch
Copy link
Member

FWIW I don't think there are any noteworthy changes in v4.0 that would interfere with this work. (The UI changes are primarily cosmetic.)

@jeffgdotorg
Copy link
Collaborator

Tagging @Julio-Oliveira-Encora so that I can assign him

@Julio-Oliveira-Encora
Copy link
Contributor

Could you please assign it to me?

@jeffgdotorg jeffgdotorg added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants