microsoft / microsoft/BootcampLabTestPlugin
Auditor adds nodes to wrong Classify branch
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Auditor adds nodes to wrong Classify branch consistently
Observed during: mcs-workflows audit (UC4/UC5), 2026-06-20
Problem: When clicking the "+" connector on a Classify node branch to add a downstream node (e.g., Agent), the auditor added the node to the wrong branch twice (Quote Request instead of Supplier Delay). The user had to intervene both times.
Root cause: The "+" buttons for each Classify branch are vertically stacked and close together on the canvas. Coordinate-based clicking is unreliable because:
- Branch order can shift depending on zoom/scroll state
- The click target area is small
- No verification is done after the node is added to confirm correct placement
Suggested fix:
- After adding a node via "+", verify which branch it connected to by reading the upstream connection label in the node config panel
- If wrong branch, delete and retry with adjusted coordinates
- Consider using the workflow designer API/model to specify target branch programmatically rather than coordinate clicking
- Alternatively, click the branch label text first to highlight/select the branch, then look for the "+" appearing specifically on that branch
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Classify-branch flow using the workflow designer and its node config panel, focusing on the stacked "+" connectors. First check whether the workflow designer API/model can identify a target branch; otherwise verify the upstream connection label after adding a node. Done means downstream nodes consistently attach to the selected branch without user intervention.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100