AI: Jira Integration

If your organization also uses Jira, Dragon Planner's MCP integration can help you export work items and keep references in sync.

How It Works

Dragon Planner doesn't call Jira directly. Instead, it provides tools that generate Jira-compatible data that you (or your AI assistant) can push to Jira through a Jira MCP server or API.

The workflow:

1. 💳 Find items to export — Use list_unsynced_items to see work items that don't have a Jira key yet
2. 📦 Generate Jira payload — Use generate_jira_payload to get a properly formatted JSON object with Jira field mappings
3. 🚀 Create in Jira — Send that payload to Jira (via their API or a Jira MCP server)
4. 🔗 Link back — Use update_jira_reference to store the Jira issue key (e.g., AUTH-42) on the Dragon Planner item

Finding Unsynced Items

"Show me work items that haven't been synced to Jira" "List unsynced stories and bugs"

You can filter by type to focus on specific item categories.

Generating Payloads

"Generate a Jira payload for WEB-42"

The AI creates a JSON object with:

• Summary — Mapped from the item title (with item number prefix)
• Description — The item's description
• Issue Type — Mapped from Dragon Planner type (Story → Story, Bug → Bug, etc.)
• Priority — Mapped to Jira priority levels
• Labels — Mapped from tags
• Dragon Planner metadata — Item number, project, and link back

Storing Jira Keys

"Set the Jira key for WEB-42 to AUTH-42" "Bulk update Jira keys: WEB-42=AUTH-42, WEB-43=AUTH-43"

Once an item exists in both systems, storing the Jira key creates a cross-reference. The Jira key is visible in the web app and searchable.

Tips

• 💡 The bulk update tool can set Jira keys for many items at once — efficient after a batch export.
• 💡 Jira payloads include a link back to Dragon Planner in the description, making it easy to navigate between systems.
• 💡 This is a one-way export flow. Changes in Jira won't automatically sync back to Dragon Planner.