Repository navigation
fix(search): keep the Jira half-terms summary tier within the all-terms match - #9129
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
[Medium impact] The PR appears safe to merge. SummaryRestricts Jira’s half-terms summary tier to issues that also match the full query.
Reviews (1) · Last reviewed commit: "test(search): normalize Jira fake rows b..." · Reviewed by Greptile |
This was referenced Oct 16, 2026
waleedlatif1
added a commit
that referenced
this pull request
Oct 16, 2026
* revert(search): restore the v0.9.23 Jira text search Reverts the Jira summary tiers (#9111, #9115, #9121, #9129). A plain Jira search again returns the all-terms text match in Jira's order, as in v0.9.23. The stemmedTerms helper stays; cross-source ranking uses it. * chore(search): stop exporting stemmedTerms now only text-match uses it
This branch was previously deployed
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.
Summary
<summary pairs> AND text ~ "<query>"), so both summary tiers only re-order the issues the all-terms search matches, as field boosting does; the every-term tier already was (a summary holding every term is a text match)Type of Change
Testing
atlassian.test.ts: new case where a summary pair match lacking a query term must not lead; it fails with the pre-fix query;lib/sim-search/livesuite passes (335 tests)Checklist
test-auditauthoring gate)