fix(jira): collect board issues via saved filter JQL#8923
Open
bujjibabukatta wants to merge 1 commit into
Open
fix(jira): collect board issues via saved filter JQL#8923bujjibabukatta wants to merge 1 commit into
bujjibabukatta wants to merge 1 commit into
Conversation
Contributor
|
I don't think this is a good idea. |
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
2 participants
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.
Fixes Jira Kanban boards silently missing issues when a board sub-filter is configured.
Previously, DevLake collected board issues via Jira Agile’s board issue endpoint, which applies the board saved filter and Kanban subQuery server-side. This caused resolved/released issues to disappear from DevLake when the subQuery excluded them.
This change collects Jira board issues through the Jira Search API using the saved board filter JQL stored on _tool_jira_boards.jql, bypassing the board-level subQuery while preserving the existing board issue association during extraction. Jira Server uses api/2/search, while Jira Cloud uses api/3/search/jql with token pagination.
Also stores the board configuration subQuery on _tool_jira_boards.sub_query for visibility/debugging.