siesa-agents 2.1.65 → 2.1.66

package/bmad/bmm/workflows/sync-epics-stories/data/templates/epic-template.json

@@ -0,0 +1,13 @@
+{
+  "provider": "jira",
+  "issueTypeName": "Epic",
+  "projectKey": "{{project_key}}",
+  "parent": "{{Parent_Key}}",
+  "summary": "Epic {{Epic Number}}: {{Epic Name}}",
+  "description": "## Epic Goal\n{{goal}}\n\n## Details\n{{description}}\n\n---\n*Source: {{file_path}}*",
+  "additional_fields": {
+    "priority": { "name": "Medium" },
+    "labels": ["prd-sync", "automated", "epic-file-sync", "{{epic-slug}}"],
+    "customfield_10011": "Epic {{Epic Number}}: {{Epic Name}}"
+  }
+}

package/bmad/bmm/workflows/sync-epics-stories/data/templates/story-template.json

@@ -0,0 +1,13 @@
+{
+  "provider": "jira",
+  "issueTypeName": "Story",
+  "projectKey": "{{project_key}}",
+  "summary": "Story {{Story ID}}: {{Story Name}}",
+  "description": "## User Story\n{{user_story}}\n\n## Acceptance Criteria\n{{acceptance_criteria}}\n\n## Dev Notes\n{{dev_notes}}\n\n---\n*Source: {{file_path}}*",
+  "parent": "{{Parent_Epic_Key}}",
+  "additional_fields": {
+    "priority": { "name": "Medium" },
+    "labels": ["prd-sync", "automated", "story-file-sync", "{{parent-epic-slug}}"],
+    "customfield_10014": "{{Parent_Epic_Key}}"
+  }
+}

package/bmad/bmm/workflows/sync-epics-stories/data/templates/subtask-template.json

@@ -0,0 +1,4 @@
+{
+   "issueIdOrKey": "{{Parent_Task_Key}}",
+   "commentBody": "## Details\n\n{{nested_bullets_content}}"
+}

package/bmad/bmm/workflows/sync-epics-stories/data/templates/task-template.json

@@ -0,0 +1,7 @@
+{
+  "provider": "jira",
+  "issueTypeName": "Sub-task",
+  "projectKey": "{{project_key}}",
+  "parent": "{{Parent_Story_Key}}",
+  "summary": "{{Story ID}} - {{Task Name}}"
+}

package/bmad/bmm/workflows/sync-epics-stories/steps/step-04-epics.md

@@ -4,7 +4,6 @@ description: 'Synchronize Epics from markdown to Jira'
 
 # Path Definitions
 workflow_path: '{project-root}/_bmad/bmm/workflows/sync-epics-stories'
-
 # File References
 thisStepFile: '{workflow_path}/steps/step-04-epics.md'
 nextStepStories: '{workflow_path}/steps/step-05-stories.md'
@@ -37,6 +36,7 @@ To read `epics.md`, check for existing Epics in Jira, create missing ones, and u
 
 - Read `{configFile}` to get `project_key` and `cloud_id`.
 - Read `{epicsFile}`.
+- **CRITICAL:** Read the epic template payload from `{project-root}/_bmad/bmm/workflows/sync-epics-stories/data/templates/epic-template.json`.
 
 ### 2. Iterate and Sync
 
@@ -54,33 +54,16 @@ For each Epic in the file:
 
     3.  **Creation (Atomic Transaction):**
 
-        -   Execute `createJiraIssue` using the following REFERENCE TEMPLATE:
+        -   Execute `createJiraIssue`. DO NOT use hardcoded JSON.
+        -   You MUST format the JSON object using the `epic-template.json` file you loaded in Step 1.
+        -   Extract the `{{Epic Number}}` (e.g., "1" from "Epic 1: Core Inventory Visibility...") and `{{Epic Name}}` from the Markdown.
+        -   Inject those, along with `{{goal}}`, `{{description}}`, and `{{project_key}}` into the template payload.
+        -   **Hierarchy Handling (CRITICAL):** Check `project_config.yaml` for `hierarchy_level_2_name`.
+            -   **If present (Custom Hierarchy):** Search for this issue using JQL to get its Key. Inject that Key into `{{Parent_Key}}` in the template.
+            -   **If absent (Standard Hierarchy):** Remove the `"parent": "{{Parent_Key}}"` property completely from the JSON payload before sending it to Jira.
 
         -   ⚠️ **CRITICAL CONSTRAINT:** `issueTypeName` MUST be exactly `"Epic"`. DO NOT translate to "Épica" or any other language. The API requires the English identifier.
 
-        
-
-        ```json
-
-        {
-
-          "provider": "jira",
-
-          "issueTypeName": "Epic",
-
-          "summary": "[Epic] {{Epic Name}}",
-
-
-      "description": "## Epic Goal\n{{goal}}\n\n## Details\n{{description}}\n\n---\n*Source: {{file_path}}*",
-      "projectKey": "{{project_key}}",
-      "additional_fields": {
-         "priority": { "name": "Medium" },
-         "labels": ["prd-sync", "automated", "epic-file-sync", "{{epic-slug}}"],
-         "customfield_10011": "{{Epic Name}}"
-      }
-    }
-    ```
-
 4.  **Immediate File Persistence (CRITICAL):**
     -   **IMMEDIATELY** after obtaining the new `key` (or finding an existing one):
     -   Update `{epicsFile}` **RIGHT NOW**. Do not wait for the loop to finish.

package/bmad/bmm/workflows/sync-epics-stories/steps/step-05-stories.md

@@ -59,6 +59,7 @@ To read story files from `{storiesFolder}`, link them to Parent Epics (found in
 - Read `{configFile}`.
 - Get list of all `.md` files in `{storiesFolder}`.
 - Read `{epicsFile}` (to lookup Parent Epic IDs).
+- **CRITICAL:** Read the template payloads from `{project-root}/_bmad/bmm/workflows/sync-epics-stories/data/templates/` (`story-template.json`, `task-template.json`, and `subtask-template.json`).
 
 ### 3. Iterate and Sync
 
@@ -94,23 +95,10 @@ For each markdown file in `{storiesFolder}`:
         -   Proceed to Step 4.
 
 4.  **Creation (Atomic Transaction - If Condition Not Found):**
-    -   Execute `createJiraIssue` using the following REFERENCE TEMPLATE:
-
-    ```json
-    {
-      "provider": "jira",
-      "issueTypeName": "Story",
-      "projectKey": "{{project_key}}",
-      "summary": "{{Story Name}}",
-      "description": "## User Story\n{{user_story}}\n\n## Description\n{{description}}\n\n## Acceptance Criteria\n{{acceptance_criteria}}\n\n---\n*Source: {{file_path}}*",
-      "parent": "{{Parent_Epic_Key}}",
-      "additional_fields": {
-         "priority": { "name": "Medium" },
-         "labels": ["prd-sync", "automated", "epic-file-sync", "{{parent-epic-slug}}"],
-         "customfield_10014": "{{Parent_Epic_Key}}" // 'Epic Link' field. IMPORTANT: Check project capability for field ID.
-      }
-    }
-    ```
+    -   Execute `createJiraIssue`. DO NOT use hardcoded JSON.
+    -   You MUST format the JSON object using `story-template.json` that you loaded in Step 2.
+    -   Extract the `{{Story ID}}` (e.g. "1.1") and `{{Story Name}}` from the Markdown file's main H1 header.
+    -   Inject those, along with `{{user_story}}`, `{{acceptance_criteria}}`, `{{dev_notes}}`, and `{{Parent_Epic_Key}}` into the template payload.
     -   **Set:** `{{KEY}}` = New Issue Key.
 
 5.  **Immediate File Persistence (CRITICAL):**
@@ -140,23 +128,9 @@ For each markdown file in `{storiesFolder}`:
                 -   Check: Is `{{Task Name}}` already present in the *already synced tasks* list?
                 -   **If YES:** **SKIP** this task. Log "Task '{{Task Name}}' already synced."
                 -   **If NO:** **PROCEED** to Create.
-            -   **Create:** Execute `createJiraIssue`:
-                ```json
-                {
-                  "provider": "jira",
-                  "issueTypeName": "Sub-task",
-                  "projectKey": "{{project_key}}",
-                  "parent": "{{KEY}}",
-                  "summary": "{{Task Text}}"
-                }
-                ```
-            -   **Context:** If the task has nested items (indented bullets), combine them into a **simple markdown bulleted list** (ensuring no checklist `[ ]` syntax is used) and execute `addCommentToJiraIssue`:
-                ```json
-                {
-                   "issueIdOrKey": "{{New_SubTask_Key}}",
-                   "commentBody": "## Details\n\n{{nested_bullets_content}}"
-                }
-                ```
+            -   **Create:** Execute `createJiraIssue` formatting the `task-template.json` loaded in Step 2.
+                -   Remember to inject `{{Story ID}}` parsed from earlier, `{{Task Name}}`, and `{{project_key}}`.
+            -   **Context:** If the task has nested items (indented bullets), combine them into a **simple markdown bulleted list** (ensuring no checklist `[ ]` syntax is used) and execute `addCommentToJiraIssue` formatting the `subtask-template.json` loaded in Step 2.
             -   **Persistence (Append Update):**
                 -   **Immediately** append a new row to the `## Synced Tasks` table (create table header if it doesn't exist yet):
                 ```markdown

package/package.json

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