Issues
- Sunflower 2025-R1 release: 3.0.0EDGCMNSPR-60Resolved issue: EDGCMNSPR-60Julian Ladisch
- Make the feign client config and component scanning happen in different classesEDGCMNSPR-59Resolved issue: EDGCMNSPR-59Matt Weaver
- Issues - HTTPS hostname wrong affecting edge-common-spring -base modulesEDGCMNSPR-58Resolved issue: EDGCMNSPR-58Oleg Kurdyayev
- Upgrade dependencies for Ramsons fixing vulnsEDGCMNSPR-57Resolved issue: EDGCMNSPR-57
- Release 2.4.5EDGCMNSPR-55Resolved issue: EDGCMNSPR-55Viachaslau Khandramai
- Release 2.4.4EDGCMNSPR-54Resolved issue: EDGCMNSPR-54Julian Ladisch
- Spring Boot 3.2.6, bcprov-jdk18on 1.78 fixing vulnsEDGCMNSPR-53Resolved issue: EDGCMNSPR-53Julian Ladisch
- Release 2.4.2EDGCMNSPR-52Resolved issue: EDGCMNSPR-52Viachaslau Khandramai
- Support HTTPS in EnrichUrlClientEDGCMNSPR-51
- Release edge-common-spring 2.4.1EDGCMNSPR-50Resolved issue: EDGCMNSPR-50Julian Ladisch
- edge-api-utils 1.4.1 fixing vault and circular dependency issuesEDGCMNSPR-49Resolved issue: EDGCMNSPR-49Julian Ladisch
- Release edge-common-spring 2.4.0 for QuesneliaEDGCMNSPR-48Resolved issue: EDGCMNSPR-48Julian Ladisch
- Spring Boot 3.2, folio-spring 8.1, edge-api-utils 1.4EDGCMNSPR-47Resolved issue: EDGCMNSPR-47Julian Ladisch
- edge-api-util 1.3.1 removing ion-java CVE-2024-21634EDGCMNSPR-46Resolved issue: EDGCMNSPR-46Julian Ladisch
- edge-common-spring: module releaseEDGCMNSPR-44Resolved issue: EDGCMNSPR-44Oleksandr Bozhko
- Spring Boot 3.1.6, folio-spring-* 7.2.2EDGCMNSPR-43Resolved issue: EDGCMNSPR-43
- edge-common-spring: module releaseEDGCMNSPR-41Resolved issue: EDGCMNSPR-41Aliaksei Harbuz
- Upgrade Folio spring base and Folio spring system user dependency versionEDGCMNSPR-40Resolved issue: EDGCMNSPR-40Vignesh Kalyanasundaram
- Implement Expired token from cache of edge-common-springEDGCMNSPR-39Resolved issue: EDGCMNSPR-39Nirmal R Shah
- Upgrade dependencies for Poppy (Spring Boot 3.1, ...)EDGCMNSPR-38Resolved issue: EDGCMNSPR-38Julian Ladisch
- Migrate to folio-spring-support v7.0.0EDGCMNSPR-35Resolved issue: EDGCMNSPR-35Vignesh Kalyanasundaram
- edge-common-spring: module releaseEDGCMNSPR-32Resolved issue: EDGCMNSPR-32Mikita Siadykh
- Update the module to Spring boot v3.0.0 and identify issues.EDGCMNSPR-31Resolved issue: EDGCMNSPR-31Bekhzod Kurbonboev
- Update to Java 17.EDGCMNSPR-30Resolved issue: EDGCMNSPR-30Bekhzod Kurbonboev
- Implement refresh token rotationEDGCMNSPR-29Resolved issue: EDGCMNSPR-29Nirmal R Shah
- Logging improvement - ConfigurationEDGCMNSPR-28Resolved issue: EDGCMNSPR-28Siarhei Charniak
- edge-common-spring: Nolana releaseEDGCMNSPR-27Resolved issue: EDGCMNSPR-27Aliaksei Harbuz
- edge-common-spring: spring upgradeEDGCMNSPR-26Resolved issue: EDGCMNSPR-26
- Logging improvementEDGCMNSPR-24
- EDGCMNSPR (edge-common-spring) MG Bugfix Release - 2.0.2EDGCMNSPR-23Resolved issue: EDGCMNSPR-23Denis
- Updating of headers processingEDGCMNSPR-22Resolved issue: EDGCMNSPR-22Siarhei Charniak
- edge-api-utils dependency updating to 1.1.2EDGCMNSPR-21Resolved issue: EDGCMNSPR-21Viachaslau Khandramai
- EDGCMNSPR (edge-common-spring) Release - 2.0.1EDGCMNSPR-20Resolved issue: EDGCMNSPR-20Viachaslau Khandramai
- EDGCMNSPR (edge-common-spring) Release - 2.x.xEDGCMNSPR-19Resolved issue: EDGCMNSPR-19
- Publish javadoc and sources to maven repositoryEDGCMNSPR-18Resolved issue: EDGCMNSPR-18
- edge-common-spring release Morning Glory R2 2022EDGCMNSPR-17Resolved issue: EDGCMNSPR-17
- edge-common-spring Spring upgrade Morning Glory 2022 R2EDGCMNSPR-16Resolved issue: EDGCMNSPR-16
- Release v2.0.0EDGCMNSPR-15Resolved issue: EDGCMNSPR-15Andrii Novytskyi
- Upgrade folio-spring-base to 4.0.0EDGCMNSPR-14Resolved issue: EDGCMNSPR-14Andrii Novytskyi
- Release edge-common-spring v1.2.0EDGCMNSPR-13Resolved issue: EDGCMNSPR-13Oleksii Kuzminov
- Logging improvementEDGCMNSPR-12Resolved issue: EDGCMNSPR-12Taras Spashchenko
- edge-common-spring: folio-spring-base updateEDGCMNSPR-11Resolved issue: EDGCMNSPR-11Pavlo Smahin
- Spring Boot 2.6EDGCMNSPR-10Resolved issue: EDGCMNSPR-10Pavlo Smahin
- edge-common-spring: folio-spring-base v3 updateEDGCMNSPR-9Resolved issue: EDGCMNSPR-9Aliaksei Harbuz
- Release-1.1.0EDGCMNSPR-8Resolved issue: EDGCMNSPR-8Vitalii_Zahoruiko
- Fix wrong throwing of Authorization exceptionEDGCMNSPR-7Resolved issue: EDGCMNSPR-7Andrii Novytskyi
- Incorrect api key param nameEDGCMNSPR-6Resolved issue: EDGCMNSPR-6Illia Borysenko
- Allow log level to be specified as system property or program argument for edge mmodulesEDGCMNSPR-5Resolved issue: EDGCMNSPR-5Roman Leshchenko
- edge-common-spring release-1.0.0EDGCMNSPR-4Resolved issue: EDGCMNSPR-4Victoria_Smelova
- Exclude swagger endpoints from security filterEDGCMNSPR-3Resolved issue: EDGCMNSPR-3Andrii Novytskyi
50 of 52
Cannot Reproduce
Details
Details
Assignee
Unassigned
UnassignedReporter
Ann-Marie Breaux
Ann-Marie Breaux(Deactivated)Priority
Development Team
Folijet
Release
Not Scheduled
RCA Group
Implementation coding issue
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created December 9, 2020 at 3:57 PM
Updated May 14, 2024 at 3:00 PM
Resolved May 14, 2024 at 3:00 PM
Overview: In Honeysuckle Bugfest, on the Data Import View all, the status sort ascending works, but not descending
Steps to Reproduce:
Log into Honeysuckle bugfest as abreaux/admin
Go to the data import app
Click View all to go to the View all log page
Click the status column header in the log list to sort ascending
Click the status column header again to sort descending
Expected Results: Ascending and descending should both work properly
Actual Results: Ascending works, descending doesn't
Additional Information: See attached video
NOTE Discussed with Data Import Subgroup - no rush to fix this; filters are good enough for now. Made it a P4 priority
Question for the UI Devs - should we disallow column sorting on the View all logs page? Once there are many, many results (like in Honeysuckle Bugfest), it seems like errors will happen.