fix(jira): collect issues via search API to avoid kanban sub-filter exclusion#8931
Open
jbsmith7741 wants to merge 3 commits into
Open
fix(jira): collect issues via search API to avoid kanban sub-filter exclusion#8931jbsmith7741 wants to merge 3 commits into
jbsmith7741 wants to merge 3 commits into
Conversation
…exclusion
* Switch from board Agile API to search API with saved filter JQL so
resolved issues (e.g. released fixVersions) are no longer silently
excluded by kanban sub-filters
* Add sub_query field to boards model and migration to track kanban
sub-filter changes across syncs
* Support JIRA Cloud v3 search/jql endpoint alongside v2 for Server
…shes * Fix Jira board SubQuery struct to match nested API response shape * Prevent click event from being stored as plugin state in connection list * Default initialValues to empty object when plugin config omits 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
1 participant
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.
Summary
Jira boards configured with kanban sub-filters silently exclude issues when collected via the standard board-issue endpoint. This PR switches issue collection to use the Jira Search API (JQL) derived from the board's filter configuration, ensuring all matching issues are ingested regardless of sub-filter settings.
Additionally fixes:
SubQuerystruct shape to correctly unmarshal the nested API responseMouseEventintoonCreate(which expects no arguments), causing the synthetic event object to be stored as plugin state. Fixed by wrapping the handler in an arrow function soonCreate()is called cleanly with no arguments.initialValues— downstream code spreads/iterates this value, so destructuring without a default producedundefinedand threw at runtime. Fixed by defaulting to{}during destructuring.Does this close any open issues?
Closes #8917
Screenshots
N/A — backend data-pipeline change with no UI impact beyond the crash fixes.
Other Information
20260611_add_sub_query_to_boards.goadds thesub_querycolumn to_tool_jira_boards.BoardConfigurationunmarshalling and the search-API issue collector.