markdown-to-jira

This conversion works by reading structured Markdown backlog blocks containing required metadata like projectKey, issueType, summary, description, component, and labels. It validates the data, creates an Epic first if present, then generates Tasks, and writes real Jira issue keys back into the document.

The required format uses structured Epic and Task blocks within a Markdown document. Each block must contain specific metadata fields: projectKey, issueType, summary, description, component, and labels, to pass validation and successfully generate Jira issues.

Yes, the conversion process supports linking tasks to epics. It automatically creates the Epic first if present in the Markdown document, then creates the Tasks and applies optional epic linkage between them via the jira_editJiraIssue function.

Yes, you can apply Jira labels and components when generating issues from Markdown. The process validates these fields within the Markdown blocks and applies them to the newly created Jira issues using the jira_editJiraIssue function.

The system validates required metadata fields like projectKey, issueType, summary, description, component, and labels within Markdown backlog blocks. It enforces this metadata before creation, ensuring blocks lacking the required information do not proceed to Jira issue generation.

Yes, context queries are supported when creating Jira tasks from Markdown. The system processes context queries present in the structured Markdown block to augment and enhance the generated Jira issue description.