Feature : add fuzzy team matching for pair programming#206
Merged
SindiBuklaji merged 6 commits intomainfrom Mar 4, 2026
Merged
Feature : add fuzzy team matching for pair programming#206SindiBuklaji merged 6 commits intomainfrom
Feature : add fuzzy team matching for pair programming#206SindiBuklaji merged 6 commits intomainfrom
Conversation
Contributor
|
🤖 No OpenAPI or client changes needed. |
…dance management
…l and whitespace handling
…ilarity calculation
d7a3f74 to
e54965f
Compare
Contributor
|
🤖 No OpenAPI or client changes needed. |
…ng whitespace handling
Contributor
|
🤖 No OpenAPI or client changes needed. |
Feature : add fuzzy team matching for pair programming
az108
approved these changes
Mar 4, 2026
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.
Checklist
General
Server
Client
Motivation and Context
Description
Implement Levenshtein distance-based fuzzy matching to handle team names that differ between Artemis and uploaded Excel files (e.g., "crop & code" vs "crop and code")
Conservative exact matching with & → and conversion for safe name normalization that works for
all teams
Aggressive fuzzy matching as fallback that removes common prefixes (Team, Group), suffixes (+ Co.
KG, Ltd., Inc.), and dots to match edge cases.
80% similarity threshold for fuzzy matching to ensure high-quality matches while catching minor
variations
Comprehensive debug logging to troubleshoot team name matching issues in production
Two-stage matching strategy: Try exact match first (safe, precise), then fuzzy match as fallback
(flexible, catches edge cases)
Steps for Testing
Prerequisites:
Review Progress
Code Review
Manual Tests
Test Coverage
Screenshots