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

Edit and delete buttons behavior when check all items on selecting multiple item with several page #13446

Closed
Zeawiel opened this issue Aug 11, 2023 · 0 comments
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

@Zeawiel
Copy link

Zeawiel commented Aug 11, 2023

NetBox version

v3.5.7

Python version

3.11

Steps to Reproduce

On demo instance:

  1. Go on cable list page
  2. Selection less item by page than the total number of cable (eg 50, the list is 108 cables)
  3. Tick the checkbox to select all item on the top row.
  4. The box "Select all 108 cables matching query" appears with edit and delete buttons activated (if clicked, edit or delete only 50 items)
  5. Tick the box "Select all 108 cables matching query", button are still activated (if clicked, edit or delete all 108 items)
  6. Untick the box "Select all 108 cables matching query", button are deactivated.

This applies to all kind of list. Not only cables.

Expected Behavior

The behavior should be the same:

  1. The edit and delete button should be activated all the time
  2. The edit and delete button should be activated only when the checkbox select all is selected.

Observed Behavior

The first time the box appears, the button are activated where they should not, if we take in consideration the action that is applies when we untick the box.

@Zeawiel Zeawiel added the type: bug A confirmed report of unexpected behavior in the application label Aug 11, 2023
@jeremystretch jeremystretch self-assigned this Aug 11, 2023
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Aug 11, 2023
@jeremystretch jeremystretch added the severity: low Does not significantly disrupt application functionality, or a workaround is available label Aug 11, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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

No branches or pull requests

2 participants