[#59781] Export of an unsaved query not working properly #17371
Merged
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
…-not-working-properly
klaustopher
approved these changes
Dec 5, 2024
|
Thanks @klaustopher ! |
as-op
deleted the
bug/59781-export-of-an-unsaved-query-not-working-properly
branch
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.
Ticket
https://community.openproject.org/work_packages/59781
What are you trying to achieve?
Fix a bug for unsaved filter changes (to a saved query) where ignores by all work package list exports (PDF/XLS/CSV).
What approach did you choose and why?
Fix a string concatenation in a stimulus controller, which was not aware of a change (added query_id parameter) in the URL from the backend.
Merge checklist