siesa-agents 2.1.27 → 2.1.29

package/bmad-core/tasks/validate-jira-auth.md

@@ -0,0 +1,251 @@
+<!-- Powered by BMAD™ Core -->
+
+# Validate Jira Authentication Task
+
+## Purpose
+
+Validate that the Jira MCP integration is properly authenticated before executing any Jira operations. This task prevents workflow disruptions caused by expired authentication sessions by proactively checking authentication status and instructing users to re-authenticate when needed.
+
+## When to Use This Task
+
+**CRITICAL:** This task MUST be executed as the FIRST step before ANY Jira MCP operation, including:
+
+- Creating epics or stories in Jira
+- Syncing PRD to Jira
+- Syncing story tasks to Jira  
+- Updating story status
+- Retrieving project information
+- Any call to `mcp_gitkraken_*` tools with `provider: "jira"`
+
+**Do NOT skip this validation** - authentication failures mid-workflow cause confusion and wasted execution.
+
+## Instructions
+
+### Step 1: Attempt Authentication Check
+
+**Action:** Make a lightweight Jira MCP call to verify authentication status
+
+```output
+🔐 Validating Jira authentication...
+```
+
+**Execute Test Call:**
+
+```action
+Call MCP Function: mcp_gitkraken_issues_assigned_to_me
+Parameters:
+  - provider: "jira"
+  - page: 1
+
+This is a lightweight call that will:
+1. Return immediately if authenticated
+2. Fail with authentication error if session expired
+3. Not create or modify any data
+```
+
+### Step 2: Interpret Response
+
+**Expected Outcomes:**
+
+#### ✅ Scenario A: Authentication Valid
+
+**Indicators:**
+- MCP call returns successfully (even if no issues found)
+- Response contains valid data structure
+- No authentication errors in response
+
+**Output:**
+```output
+✅ Jira authentication verified
+✅ MCP connection active
+```
+
+**Action:** Return success and allow workflow to continue
+
+---
+
+#### ❌ Scenario B: Authentication Expired/Invalid
+
+**Indicators:**
+- MCP call fails with authentication error
+- Error message contains: "unauthorized", "authentication", "token expired", "session expired"
+- HTTP 401 or 403 error codes
+- No valid response data
+
+**Output:**
+```output
+═══════════════════════════════════════════════════════════════
+  ⚠️  AUTENTICACIÓN DE JIRA REQUERIDA
+═══════════════════════════════════════════════════════════════
+
+❌ La sesión de Jira MCP ha expirado o no está autenticada.
+
+Para continuar con operaciones de Jira, debes re-autenticarte:
+
+📋 PASOS PARA RE-AUTENTICACIÓN:
+
+1. Abre el panel de MCP en VS Code:
+   - Presiona Ctrl+Shift+P (Cmd+Shift+P en Mac)
+   - Busca: "MCP: Show MCP Panel"
+   - O usa el atajo si está configurado
+
+2. En el panel de MCP:
+   - Localiza el servidor "GitKraken Jira"
+   - Haz clic en "Connect" o "Authenticate"
+   - Se abrirá una ventana del navegador
+
+3. Completa la autenticación OAuth:
+   - Inicia sesión en Jira Cloud si es necesario
+   - Autoriza el acceso para GitKraken MCP
+   - Espera la confirmación de conexión exitosa
+
+4. Verifica la conexión:
+   - El icono de GitKraken Jira debe mostrar "Connected"
+   - Cierra el navegador y regresa a VS Code
+
+5. Reintenta el comando:
+   - Vuelve a ejecutar el comando que falló
+   - La autenticación ahora debe estar activa
+
+═══════════════════════════════════════════════════════════════
+
+❌ NO PUEDO CONTINUAR hasta que completes la re-autenticación.
+
+Razón: Las operaciones de Jira requieren autenticación válida para:
+- Crear/actualizar issues
+- Consultar información del proyecto
+- Sincronizar datos entre documentos locales y Jira
+
+Una vez que hayas completado los pasos arriba, confirma escribiendo:
+"autenticado" o "listo" para continuar.
+
+═══════════════════════════════════════════════════════════════
+```
+
+**CRITICAL:** HALT execution completely. Do NOT:
+- Attempt to continue with Jira operations
+- Try to re-authenticate programmatically  
+- Make additional MCP calls
+- Suggest workarounds or alternatives
+
+**Action:** Wait for user confirmation that they have re-authenticated
+
+---
+
+#### 🔧 Scenario C: MCP Not Available
+
+**Indicators:**
+- MCP tool not found
+- MCP server not running
+- GitKraken MCP integration not installed
+
+**Output:**
+```output
+═══════════════════════════════════════════════════════════════
+  ⚠️  MCP DE JIRA NO DISPONIBLE
+═══════════════════════════════════════════════════════════════
+
+❌ El servidor MCP de GitKraken no está disponible.
+
+Posibles causas:
+- MCP no está instalado
+- El servidor MCP no está ejecutándose  
+- Configuración de MCP incorrecta
+
+📋 PASOS PARA CONFIGURAR MCP:
+
+1. Verifica que GitKraken MCP esté instalado
+2. Revisa la configuración de MCP en VS Code
+3. Reinicia el servidor MCP si es necesario
+4. Contacta al administrador si el problema persiste
+
+═══════════════════════════════════════════════════════════════
+
+❌ NO PUEDO CONTINUAR sin acceso al MCP de Jira.
+
+HALT execution.
+```
+
+### Step 3: User Confirmation (If Re-auth Required)
+
+```elicit
+path: Wait for user re-authentication confirmation
+format: |
+  ⏳ Esperando confirmación de re-autenticación...
+  
+  Has completado los pasos de autenticación en el panel de MCP?
+  
+  Opciones:
+  1. Sí, estoy autenticado - verificar de nuevo
+  2. Necesito ayuda con la autenticación
+  3. Cancelar operación
+  
+  Ingresa tu selección (1-3):
+```
+
+**If Option 1:** Retry Step 1 to verify authentication
+**If Option 2:** Display detailed troubleshooting guide
+**If Option 3:** Exit task gracefully
+
+### Step 4: Retry Verification (After User Confirms)
+
+**Action:** Repeat Step 1 to confirm authentication is now valid
+
+- [ ] Execute test MCP call again
+- [ ] Verify successful response
+- [ ] Return success if authenticated
+- [ ] If still fails, return to Step 2
+
+**Success Output:**
+```output
+✅ Re-autenticación exitosa
+✅ Conexión a Jira verificada
+✅ Listo para continuar con operaciones de Jira
+```
+
+## Integration Points
+
+**This task should be called from:**
+
+- `sync-prd-to-jira.md` - Before Phase 1, Step 1
+- `sync-story-to-jira.md` - Before Phase 1, Step 1  
+- `update-story-jira-status.md` - Before Phase 1, Step 3
+- `jira-setup.md` - Before Phase 2, Step 3
+- Any other task that uses Jira MCP
+
+**Add this step to task instructions:**
+
+```markdown
+#### Step 0: Validate Jira Authentication (REQUIRED)
+
+**Action:** Execute `validate-jira-auth.md` task
+
+- [ ] Call validate-jira-auth task
+- [ ] Verify authentication is active
+- [ ] Only proceed if validation passes
+
+**If validation fails:** HALT and instruct user to re-authenticate before continuing.
+```
+
+## Error Recovery
+
+**Common Authentication Errors:**
+
+| Error Pattern | Meaning | Solution |
+|---------------|---------|----------|
+| `401 Unauthorized` | Token expired | Re-authenticate via MCP panel |
+| `403 Forbidden` | Insufficient permissions | Check Jira access rights |
+| `oauth_token_expired` | OAuth session expired | Re-authenticate via MCP panel |
+| `ETIMEDOUT` | Network/MCP connection issue | Check MCP server status |
+
+## Notes
+
+- Authentication sessions typically expire after inactivity
+- OAuth tokens may have time-based expiration (e.g., 1 hour, 24 hours)
+- Re-authentication does NOT require reconfiguring project settings
+- `docs/jira-conf.md` configuration remains valid after re-auth
+
+---
+
+**Last Updated:** 2025-12-11  
+**Task Version:** 1.0.0

package/bmad-core/templates/jira-conf-tmpl.md

@@ -0,0 +1,13 @@
+# Jira Project Configuration
+
+**Project Key:** `{PROJECT_KEY}`
+**Project Name:** `{PROJECT_NAME}`
+**Cloud ID:** `{CLOUD_ID}`
+
+## Available Story Statuses
+
+_This section will be automatically populated when first using `*update-story-jira-status` command. Statuses are retrieved from Jira via MCP and cached here for efficiency._
+
+---
+
+_Note: Project Key, Project Name, and Cloud ID were automatically retrieved during `*jira-setup`. Available Story Statuses will be auto-populated on first use._

package/claude/commands/BMad/agents/dev.md

@@ -73,6 +73,7 @@ commands:
   - explain: teach me what and why you did whatever you just did in detail so I can learn. Explain to me as if you were training a junior engineer.
   - review-qa: run task `apply-qa-fixes.md'
   - run-tests: Execute linting and tests
+  - update-story-jira-status {story}: run task `update-story-jira-status.md` with the provided story file - Update story status in Jira with validation of tasks completion and QA gates
   - exit: Say goodbye as the Developer, and then abandon inhabiting this persona
 
 dependencies:
@@ -81,5 +82,7 @@ dependencies:
   tasks:
     - apply-qa-fixes.md
     - execute-checklist.md
+    - update-story-jira-status.md
+    - validate-jira-auth.md
     - validate-next-story.md
 ```

package/claude/commands/BMad/agents/pm.md

@@ -69,6 +69,8 @@ commands:
   - create-story: Create user story from requirements (task brownfield-create-story)
   - doc-out: Output full document to current destination file
   - shard-prd: run the task shard-doc.md for the provided prd.md (ask if not found)
+  - sync-epic-files-to-jira: Sync individual epic files from docs/prd/ to Jira (task sync-epic-files-to-jira.md)
+  - sync-prd-to-jira: Automatically create Jira epics and stories from PRD (task sync-prd-to-jira.md)
   - yolo: Toggle Yolo Mode
   - exit: Exit (confirm)
 dependencies:
@@ -76,6 +78,7 @@ dependencies:
     - change-checklist.md
     - pm-checklist.md
   data:
+    - jira-preferences.md
     - technical-preferences.md
   tasks:
     - brownfield-create-epic.md
@@ -85,6 +88,9 @@ dependencies:
     - create-doc.md
     - execute-checklist.md
     - shard-doc.md
+    - sync-epic-files-to-jira.md
+    - sync-prd-to-jira.md
+    - validate-jira-auth.md
   templates:
     - brownfield-prd-tmpl.yaml
     - prd-tmpl.yaml

package/claude/commands/BMad/agents/po.md

@@ -34,6 +34,7 @@ activation-instructions:
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
   - STAY IN CHARACTER!
   - CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
+  - JIRA CONFIGURATION CHECK: Before executing sync-story-to-jira command, ALWAYS check if docs/jira-conf.md exists. If NOT found, inform user that project-specific Jira configuration is required and offer to run `*jira-setup` command to create it interactively.
 agent:
   name: Sarah
   id: po
@@ -41,6 +42,15 @@ agent:
   icon: 📝
   whenToUse: Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions
   customization: null
+jira-config:
+  project-config-file: docs/jira-conf.md
+  global-preferences-file: .bmad-core/data/jira-preferences.md
+  required-project-fields:
+    - cloud-id: Jira Cloud ID (UUID format)
+    - jira-url: Full Jira instance URL
+    - project-key: Jira project key (e.g., PM, PROJ)
+    - project-name: Human-readable project name
+  validation: Auto-check docs/jira-conf.md before Jira operations, prompt for setup if missing
 persona:
   role: Technical Product Owner & Process Steward
   style: Meticulous, analytical, detail-oriented, systematic, collaborative
@@ -68,7 +78,11 @@ commands:
   - create-story: Create user story from requirements (task brownfield-create-story)
   - doc-out: Output full document to current destination file
   - execute-checklist-po: Run task execute-checklist (checklist po-master-checklist)
+  - jira-setup: Configure Jira integration (provider, project, organization)
   - shard-doc {document} {destination}: run the task shard-doc against the optionally provided document to the specified destination
+  - sync-story-to-jira {story}: Sync approved story tasks/subtasks to Jira (task sync-story-to-jira)
+  - sync-epic-to-jira {epic-number}: Sync all approved stories from an epic to Jira (task sync-stories-batch-to-jira with scope epic-N)
+  - update-epic-status {epic-number}: Batch update status of all stories in an epic (task update-epic-stories-jira-status)
   - validate-story-draft {story}: run the task validate-next-story against the provided story file
   - yolo: Toggle Yolo Mode off on - on will skip doc section confirmations
   - exit: Exit (confirm)
@@ -76,11 +90,18 @@ dependencies:
   checklists:
     - change-checklist.md
     - po-master-checklist.md
+  data:
+    - jira-preferences.md
   tasks:
     - correct-course.md
     - execute-checklist.md
+    - jira-setup.md
     - shard-doc.md
+    - sync-story-to-jira.md
+    - update-epic-stories-jira-status.md
+    - validate-jira-auth.md
     - validate-next-story.md
   templates:
+    - jira-conf-tmpl.md
     - story-tmpl.yaml
 ```

package/claude/settings.local.json

@@ -1,4 +1,7 @@
 {
+  "enabledMcpjsonServers": [
+    "atlassian"
+  ],
   "permissions": {
     "allow": [
       "Bash(node:*)",

package/github/chatmodes/dev.chatmode.md

@@ -80,6 +80,7 @@ commands:
   - explain: teach me what and why you did whatever you just did in detail so I can learn. Explain to me as if you were training a junior engineer.
   - review-qa: run task `apply-qa-fixes.md'
   - run-tests: Execute tests and validations (dotnet test for backend with xUnit, npm test for frontend with Vitest, dotnet format for code style, code analyzers)
+  - update-story-jira-status {story}: run task `update-story-jira-status.md` with the provided story file - Update story status in Jira with validation of tasks completion and QA gates
   - build: Build solution (dotnet build for backend, npm run build for frontend)
   - restore: Restore dependencies (dotnet restore for NuGet packages, npm install for Node packages)
   - exit: Say goodbye as the Developer, and then abandon inhabiting this persona
@@ -90,5 +91,7 @@ dependencies:
   tasks:
     - apply-qa-fixes.md
     - execute-checklist.md
+    - update-story-jira-status.md
+    - validate-jira-auth.md
     - validate-next-story.md
 ```

package/github/chatmodes/pm.chatmode.md

@@ -67,6 +67,8 @@ commands:
   - create-story: Create user story from requirements (task brownfield-create-story)
   - doc-out: Output full document to current destination file
   - shard-prd: run the task shard-doc.md for the provided prd.md (ask if not found)
+  - sync-epic-files-to-jira: Sync individual epic files from docs/prd/ to Jira (task sync-epic-files-to-jira.md)
+  - sync-prd-to-jira: Automatically create Jira epics and stories from PRD (task sync-prd-to-jira.md)
   - yolo: Toggle Yolo Mode
   - exit: Exit (confirm)
 dependencies:
@@ -74,6 +76,7 @@ dependencies:
     - change-checklist.md
     - pm-checklist.md
   data:
+    - jira-preferences.md
     - technical-preferences.md
   tasks:
     - brownfield-create-epic.md
@@ -83,6 +86,9 @@ dependencies:
     - create-doc.md
     - execute-checklist.md
     - shard-doc.md
+    - sync-epic-files-to-jira.md
+    - sync-prd-to-jira.md
+    - validate-jira-auth.md
   templates:
     - brownfield-prd-tmpl.yaml
     - prd-tmpl.yaml

package/github/chatmodes/po.chatmode.md

@@ -42,6 +42,15 @@ agent:
   icon: 📝
   whenToUse: Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions
   customization: null
+jira-config:
+  project-config-file: docs/jira-conf.md
+  global-preferences-file: .bmad-core/data/jira-preferences.md
+  required-project-fields:
+    - cloud-id: Jira Cloud ID (UUID format)
+    - jira-url: Full Jira instance URL
+    - project-key: Jira project key (e.g., PM, PROJ)
+    - project-name: Human-readable project name
+  validation: Auto-check docs/jira-conf.md before Jira operations, prompt for setup if missing
 persona:
   role: Technical Product Owner & Process Steward
   style: Meticulous, analytical, detail-oriented, systematic, collaborative
@@ -67,6 +76,8 @@ commands:
   - doc-out: Output full document to current destination file
   - execute-checklist-po: Run task execute-checklist (checklist po-master-checklist)
   - shard-doc {document} {destination}: run the task shard-doc against the optionally provided document to the specified destination
+  - sync-story-to-jira {story}: Sync approved story tasks/subtasks to Jira (task sync-story-to-jira)
+  - sync-epic-to-jira {epic-number}: Sync all approved stories from an epic to Jira (task sync-stories-batch-to-jira with scope epic-N)
   - validate-story-draft {story}: run the task validate-next-story against the provided story file
   - yolo: Toggle Yolo Mode off on - on will skip doc section confirmations
   - exit: Exit (confirm)
@@ -74,11 +85,16 @@ dependencies:
   checklists:
     - change-checklist.md
     - po-master-checklist.md
+  data:
+    - jira-preferences.md
   tasks:
     - correct-course.md
     - execute-checklist.md
     - shard-doc.md
-    - validate-next-story.md
+    - sync-story-to-jira.md
+    - validate-jira-auth.md
+    - validate-next-story.md    
   templates:
+    - jira-conf-tmpl.md
     - story-tmpl.yaml
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "siesa-agents",
-  "version": "2.1.27",
+  "version": "2.1.29",
   "description": "Paquete para instalar y configurar agentes SIESA en tu proyecto",
   "main": "index.js",
   "bin": {

package/vscode/mcp.json

@@ -6,6 +6,10 @@
         "shadcn@latest",
         "mcp"
       ]
+    },
+    "atlassian-mcp-server": {
+      "url": "https://mcp.atlassian.com/v1/sse",
+      "type": "http"
     }
   }
 }