From 8c23feb7cf48f8421e4436a56ec91bb49477e674 Mon Sep 17 00:00:00 2001 From: VinPropane Date: Wed, 8 Apr 2026 23:15:58 -0400 Subject: [PATCH] chore: require Jira transition choice in story-end rule --- .cursor/rules/story-end.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.cursor/rules/story-end.md b/.cursor/rules/story-end.md index 31d5fbe..55683f5 100644 --- a/.cursor/rules/story-end.md +++ b/.cursor/rules/story-end.md @@ -27,9 +27,11 @@ If the user asks to **push** changes that sit on **`main`** and **`git push orig - Do **not** delete **`main`** or **`origin/*`**. - Do **not** assume the remote story branch should be deleted unless the user asks (many teams keep `origin/NEON-…` for history or delete via GitHub UI). -## 4. Jira (optional) +## 4. Jira transition -- If the issue should move to **Done** (or equivalent), use Atlassian MCP when available; otherwise the user updates the board. This rule does **not** require Jira transitions. +- Before finishing the story-end workflow, ask the user where the Jira story should move next: **`In Test`** or **`Done`**. +- After the user chooses one of those two states, perform the Jira transition with Atlassian MCP when available. +- If Atlassian MCP is unavailable or cannot complete the transition, tell the user and ask them to update the board manually. ## Related