starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 16:26:09 +03:00

[GH-ISSUE #1803] Best Practice Analyser sorting not working correctly #953

New issue

Closed

opened 2026-03-02 13:40:19 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 13:40:19 +03:00

Owner

Originally created by @stienjo1993 on GitHub (Oct 13, 2023).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1803

Description

When you sort on current secure score in the Best Practice Analyser and set rows per page on 500, its not sorting correctly.
See picture.

Environment data

Non-sponsored instance
Front end version number: 4.4.0
Back end version number: 4.4.0
Tried Tenant Cache Clear: true
Tried Token Cache Clear: true

Originally created by @stienjo1993 on GitHub (Oct 13, 2023). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1803 ### Description When you sort on current secure score in the Best Practice Analyser and set rows per page on 500, its not sorting correctly. See picture. ![sorting](https://github.com/KelvinTegelaar/CIPP/assets/129944407/e8ddddf5-fda4-4150-8110-b5884ba84b7c) ### Environment data ```PowerShell Non-sponsored instance Front end version number: 4.4.0 Back end version number: 4.4.0 Tried Tenant Cache Clear: true Tried Token Cache Clear: true ```

kerem

2026-03-02 13:40:19 +03:00

closed this issue
added the
bug

unconfirmed-by-user
labels

kerem commented

2026-03-02 13:40:21 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 13, 2023):

Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.".

Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

@github-actions[bot] commented on GitHub (Oct 13, 2023): Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/ If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.". Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

kerem commented

2026-03-02 13:40:21 +03:00

Author

Owner

@stienjo1993 commented on GitHub (Oct 13, 2023):

I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.

@stienjo1993 commented on GitHub (Oct 13, 2023): I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.

kerem commented

2026-03-02 13:40:21 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Oct 16, 2023):

Fixed in dev.

@KelvinTegelaar commented on GitHub (Oct 16, 2023): Fixed in dev.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/CIPP#953

No description provided.

Rows
Columns