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

page list reset select2 multi-selected values. #3072

Closed
a31amit opened this issue Apr 15, 2019 · 0 comments
Closed

page list reset select2 multi-selected values. #3072

a31amit opened this issue Apr 15, 2019 · 0 comments
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@a31amit
Copy link

a31amit commented Apr 15, 2019

Environment

  • Python version: 3.7
  • NetBox version: 2.5.10

Paging results and changing the list from 50 to more devices resets back all search results and using last value by alphabet to search.

It seems like it is affecting to all multiple select options such as site, tenant, model.

Steps to Reproduce

  1. Make sure you have default devices show as 50 in dcim/devices and have more than 50 devices.
  2. filter devices with any of multi-select fields such as site, tenants, manufacture, at-least 2 values in the same field.
  3. change page list size from 50 to 100.
  4. It displays results for only for one value. last value in alphabet order always.
  5. search boxes also show values for only 1 item rather all those items

Expected Behavior

It should show results from both or all items used in the filter.

Observed Behavior

It displays results for only for one value. last value in alphabet order always.
Hence page list & multi-select not showing all the results.

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application labels Apr 15, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jan 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants