obsidian-jira

To sync Jira issues into Obsidian notes, this Skill scans issues via Atlassian MCP using JQL queries, classifies them into predefined project folders, and generates concise summaries with links and properties. It supports incremental updates and safeguards against duplicates without modifying source Jira data.

Yes, you can organize Jira issues by project automatically. The Skill classifies issues extracted through Atlassian MCP into predefined project folders and generates human-readable Obsidian notes with wiki synchronization, ensuring structured project management documentation.

The obsidian-jira workflow does not modify source Jira data. It strictly reads issues via Atlassian MCP using JQL and creates human-readable Obsidian notes with summaries and links, ensuring your original Jira project management data remains untouched.

The Jira to Obsidian workflow is triggered using the /obsidian-jira command. It supports several options including --all, --list, --stats, -p, -d, and -n to control the extraction, categorization, and wiki synchronization of Jira issues.

Incremental updating works by scanning Jira issues via Atlassian MCP using JQL and applying safeguards for duplicates. This ensures that only new or updated issues are categorized into project folders and synced to Obsidian notes, preventing redundant documentation.

Yes, Atlassian MCP is required to extract Jira issues for Obsidian notes. The workflow relies on Atlassian MCP to execute JQL queries, scan issues, and classify them into predefined project folders before generating the final summaries and wiki links.