Correct the query to accurately count overdue tickets#99
Merged
haiphucnguyen merged 1 commit intoflowinquiry:mainfrom Mar 10, 2025
Merged
Correct the query to accurately count overdue tickets#99haiphucnguyen merged 1 commit intoflowinquiry:mainfrom
haiphucnguyen merged 1 commit intoflowinquiry:mainfrom
Conversation
In my local installation, I discovered that the query counting overdue tickets per time range is incorrect. The query retrieves data by joining requests with workflow transition history but only considers the latest entry
haiphucnguyen
approved these changes
Mar 10, 2025
Collaborator
haiphucnguyen
left a comment
There was a problem hiding this comment.
Thank you, let I write some tests for it.
This file contains hidden or 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
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.
In my local installation, I discovered that the query counting overdue tickets per time range is incorrect. The query retrieves data by joining requests with workflow transition history but only considers the latest entry
Description
Changes Made
Additional Notes