From 6731ef44ea33c0ed8f3b20629f2cca7046f576c1 Mon Sep 17 00:00:00 2001 From: cabana8471 Date: Sun, 25 Jan 2026 12:07:36 +0100 Subject: [PATCH] fix: use consistent priority increment when skipping features (#65) The REST API skip endpoint was using max_priority + 1000, while the MCP server used max_priority + 1. This caused priority inflation where values could reach 10,000+ after multiple skips. Changed to use + 1 for consistency with mcp_server/feature_mcp.py:345. Fixes: leonvanzyl/autocoder#65 Co-Authored-By: Claude Opus 4.5 --- server/routers/features.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/server/routers/features.py b/server/routers/features.py index a830001..e5ad919 100644 --- a/server/routers/features.py +++ b/server/routers/features.py @@ -551,9 +551,9 @@ async def skip_feature(project_name: str, feature_id: int): if not feature: raise HTTPException(status_code=404, detail=f"Feature {feature_id} not found") - # Set priority to max + 1000 to push to end + # Set priority to max + 1 to push to end (consistent with MCP server) max_priority = session.query(Feature).order_by(Feature.priority.desc()).first() - feature.priority = (max_priority.priority if max_priority else 0) + 1000 + feature.priority = (max_priority.priority if max_priority else 0) + 1 session.commit()