Change Details

**Description** .... As a newcomer, I want the links suggested to be the relevant, because then my edit is more likely to be valuable. Tune the service parameters for underlinked tasks so instead of trying to link the first few linkable words it finds, it suggests some of the most relevant links. Follow up from T301096. **Acceptance Criteria** Given I'm a logged in user, When I received "Add a Link" suggestions, Then they are the most relevant suggestions available #### Completion checklist **Functionality** [] The patches have been code reviewed and merged [] The task passes its acceptance criteria **Engineering** [] There are existing and passing unit/integration tests [] Tests for every involved patch should pass [] Coverage for every involved project should have improved or stayed the same **Design & QA** [] If the task is UX/Design related: it must be reviewed and approved by the UX/Design team [] Must be reviewed and approved by Quality Assurance. **Documentation** [] Related and updated documentation done where necessary - Internal technical changes: internal repository documentation must be updated (README.md, JSDoc, PHPDoc) - Infrastructure technical changes: technical changes that reflect on environment, infrastructure, endpoints or any other area of interest for technical contributors should be reflected on [[ https://www.mediawiki.org/wiki/Extension:GrowthExperiments | Extension:GrowthExperiments ]] or [[ https://www.mediawiki.org/wiki/Extension:GrowthExperiments/Technical_documentation | Extension:GrowthExperiments/Technical documentation ]] pages.

**Description** As a newcomer, I want the links suggested to be the relevant, because then my edit is more likely to be valuable. Tune the service parameters for underlinked tasks so instead of trying to link the first few linkable words it finds, it suggests some of the most relevant links. Follow up from T301096. **Acceptance Criteria** Given I'm a logged in user, When I received "Add a Link" suggestions, Then they are the most relevant suggestions available #### Completion checklist **Functionality** [] The patches have been code reviewed and merged [] The task passes its acceptance criteria **Engineering** [] There are existing and passing unit/integration tests [] Tests for every involved patch should pass [] Coverage for every involved project should have improved or stayed the same **Design & QA** [] If the task is UX/Design related: it must be reviewed and approved by the UX/Design team [] Must be reviewed and approved by Quality Assurance. **Documentation** [] Related and updated documentation done where necessary - Internal technical changes: internal repository documentation must be updated (README.md, JSDoc, PHPDoc) - Infrastructure technical changes: technical changes that reflect on environment, infrastructure, endpoints or any other area of interest for technical contributors should be reflected on [[ https://www.mediawiki.org/wiki/Extension:GrowthExperiments | Extension:GrowthExperiments ]] or [[ https://www.mediawiki.org/wiki/Extension:GrowthExperiments/Technical_documentation | Extension:GrowthExperiments/Technical documentation ]] pages.

**Description** .... As a newcomer, I want the links suggested to be the relevant, because then my edit is more likely to be valuable. Tune the service parameters for underlinked tasks so instead of trying to link the first few linkable words it finds, it suggests some of the most relevant links. Follow up from T301096. **Acceptance Criteria** Given I'm a logged in user, When I received "Add a Link" suggestions, Then they are the most relevant suggestions available #### Completion checklist **Functionality** [] The patches have been code reviewed and merged [] The task passes its acceptance criteria **Engineering** [] There are existing and passing unit/integration tests [] Tests for every involved patch should pass [] Coverage for every involved project should have improved or stayed the same **Design & QA** [] If the task is UX/Design related: it must be reviewed and approved by the UX/Design team [] Must be reviewed and approved by Quality Assurance. **Documentation** [] Related and updated documentation done where necessary - Internal technical changes: internal repository documentation must be updated (README.md, JSDoc, PHPDoc) - Infrastructure technical changes: technical changes that reflect on environment, infrastructure, endpoints or any other area of interest for technical contributors should be reflected on [[ https://www.mediawiki.org/wiki/Extension:GrowthExperiments | Extension:GrowthExperiments ]] or [[ https://www.mediawiki.org/wiki/Extension:GrowthExperiments/Technical_documentation | Extension:GrowthExperiments/Technical documentation ]] pages.