-
Notifications
You must be signed in to change notification settings - Fork 23
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
feat: reactivate natural sorting order of notification by status #779
Closed
poojapatel23
wants to merge
254
commits into
eclipse-tractusx:main
from
Cofinity-X-Archive:feature/status-according-to-the-natural-order
Closed
feat: reactivate natural sorting order of notification by status #779
poojapatel23
wants to merge
254
commits into
eclipse-tractusx:main
from
Cofinity-X-Archive:feature/status-according-to-the-natural-order
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tons and connect asset publisher
Merge pull request eclipse-tractusx#765 from catenax-ng/main
…oauth-client-scope Feature/698 oauth client scope
…ing-update Security/spring update
… it will per saved as error.
… it will per saved as error.
… it will per saved as error.
…x-cypress chore(feature): 616 - Cypress test fix.
…x-notification-flow Chore/616 fix notification flow
…e-helm-release-1.3.33 Prepare Helm release for next version
feature: 616 Allow edc notification update with empty asset list, release 10.8.0
chore(release): 10.8.1
…e-helm-release-1.3.34 Prepare Helm release for next version
chore(release): 10.8.1
…repare-helm-release-1.3.34 Prepare Helm release for next version
release 10.8.1
…tatus [Summary]: - This commit provides the sorting order of notifications (alerts and investigations) to follow a natural sorting order based on status. Previously, the sorting method was sorted alphabetically [Changes Made]: - Modified/Added the SQL query responsible for sorting notifications by status. [Context/Reasoning]: - Natural sorting by status provides a more intuitive and user-friendly display of notifications.
…natural-order' into feature/status-according-to-the-natural-order # Conflicts: # tx-backend/src/main/java/org/eclipse/tractusx/traceability/notification/infrastructure/notification/model/NotificationMessageBaseEntity.java
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a new feature: reactivate natural sorting order of notifications by status
[Issue]:
[Summary]:
[Changes Made]:
[Context/Reasoning]: