Repository navigation
fix: collaboration work grouping - #3283
Merged
Merged
Conversation
…k items A Teams chat is extracted once it has been quiet for 10 minutes (at most 30 minutes of waiting), so a burst of short lines becomes one set of candidates instead of one per sync. Each extract window also gets the six messages before it as context, and the prompt asks for one candidate per ask, named from the whole conversation.
…tions - Grouping reads each thread's current primary topic, not the one stored at extraction. - An item under another topic is offered, and can take a candidate, only through a thread that already feeds it. Each candidate lists the items its thread feeds. - An item holding 15 open steps takes no more. - News that comes back as new_step becomes an item update, never a step. - Unfiled threads make items only from one conversation and skip the second grouping pass. - The second pass sees each task's thread and no longer pushes to group. - Near-identical asks under two different topics are no longer folded together.
Each thread's extract stands alone, so one run reads several in parallel. RDF_Map COLLAB_WORK_EXTRACT_PARALLEL sets how many (default 5).
…items An assignee the model names outside the thread's people is stored as unclear, and a step whose assignee is not a known person is saved without one. Grouping repeats until no candidates are pending, so one build places more than 400.
BrainPreviewTopicMatches(resort=[true]) scores the topic's Brain-filed conversations again and lists the ones it no longer fits, with the topic that fits now or none. BrainApplyTopicMatches moves them with toTopicId or takes the topic off with reject. The classifier only adds links, so this is how a Brain filing leaves a topic once the owner narrows it.
Contributor
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
kunal0137
force-pushed
the
fix-collaboration-work-grouping
branch
from
November 6, 2026 17:37
5239597 to
f31d473
Compare
kunal0137
marked this pull request as ready for review
November 6, 2026 17:43
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.
Description
Changes Made
How to Test
Notes