Repository navigation
improvement(search): fall back to Jira summaries holding half the terms of a longer query - #9115
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
There was a problem hiding this comment.
All reported issues were addressed across 3 files
Reply with feedback, questions, or to request a fix.
Turn on auto-fix | Re-trigger cubic
[Medium impact] The PR appears safe to merge; no actionable issues remain from this review. SummaryJira searches that overflow a page can now lead with summaries containing at least half the query terms when no summary contains them all.
|
…ider pool, most terms first
|
@cubic-dev-ai review this PR |
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
…descriptions only when filtered
|
@cubic-dev-ai review this PR |
@waleedlatif1 I have started the AI code review. It will take a few minutes to complete. |
* 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
Summary
jiraTextClausetakes the field (textorsummary), replacing the separate summary helperType of Change
Testing
atlassian.test.ts: 6 new cases (half-terms summaries lead and a summary below half is dropped, two-term and word-plus-plural queries skip the fallback, most terms first, matches beyond the first pair page, a failed half search keeps the all-terms page and cursor); each guard reverted and its test went red, including cancellation through the parallel searchesChecklist
test-auditauthoring gate)