Skip to content

Conversation

@Bhanuagr
Copy link
Contributor

Describe your changes:

Fixes

I worked on ... because ...

Type of change:

  • Bug fix
  • Improvement
  • New feature
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation

Checklist:

  • I have read the CONTRIBUTING document.
  • My PR title is Fixes <issue-number>: <short explanation>
  • I have commented on my code, particularly in hard-to-understand areas.
  • For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

@harshach
Copy link
Collaborator

@Bhanuagr did we check if its affecting other entities not just glossary?

@Bhanuagr
Copy link
Contributor Author

@Bhanuagr did we check if its affecting other entities not just glossary?

@harshach Its fixing issue for glossary terms and sub domains search results which uses hierarchy search

@sonarqubecloud
Copy link

@Bhanuagr Bhanuagr merged commit 8a7211e into main Dec 17, 2025
25 of 26 checks passed
@Bhanuagr Bhanuagr deleted the fix/glossary_term_search_relevance_scoring branch December 17, 2025 16:30
@github-actions
Copy link
Contributor

Changes have been cherry-picked to the 1.11.4 branch.

github-actions bot pushed a commit that referenced this pull request Dec 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backend safe to test Add this label to run secure Github workflows on PRs To release Will cherry-pick this PR into the release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants