Bridge Jira and beads: Import Jira issues locally, work with git-backed issue tracking, sync changes back to Jira.
jira-beads-sync synchronizes Jira issues with beads, a git-backed issue tracker. Work with Jira issues as YAML files in your repository, manage them with beads commands or Claude Code, then sync your changes back to Jira.
Perfect for developers who want to:
- Track Jira issues alongside code in version control
- Work with issues offline using beads
- Use natural language with Claude Code to manage issues
- Maintain bidirectional sync between Jira and local git repos
π New to jira-beads-sync? β Getting Started Guide
π― Use Cases:
- CLI User? β CLI Guide - Complete command reference
- Claude Code User? β Plugin Guide - Natural language workflows
- Need Examples? β Real-World Examples - Practical scenarios
π©βπ» For Developers:
- CLAUDE.md - Architecture and development guide
- CONTRIBUTING.md - Contribution guidelines
# Import a Jira issue with all its dependencies
jira-beads-sync quickstart PROJ-123
# Work locally with beads
bd list
bd show proj-123
bd update proj-123 --status in_progress
# Sync changes back to Jira
jira-beads-sync syncOr use natural language with Claude Code:
You: Import PROJ-123 from Jira
Claude: [Imports issue and dependencies]
β Fetched 5 issue(s)
Ready to work!
- β Bidirectional Sync: Import from Jira β Work locally β Push back to Jira
- β Automatic Dependencies: Recursively fetches epics, stories, subtasks, and links
- β Two Interfaces: CLI commands or natural language with Claude Code
- β Preserves Structure: Maintains hierarchies, relationships, and metadata
- β
Git-Backed: Issues stored as YAML files in
.beads/directory - β Type-Safe: Built on Protocol Buffers for reliability
# Direct install (recommended)
brew install conallob/tap/jira-beads-sync
# Or tap first, then install
brew tap conallob/tap
brew install jira-beads-syncDownload from the releases page or:
# macOS (Apple Silicon)
curl -LO https://github.com/conallob/jira-beads-sync/releases/latest/download/jira-beads-sync_Darwin_arm64.tar.gz
tar xzf jira-beads-sync_Darwin_arm64.tar.gz
sudo mv jira-beads-sync /usr/local/bin/
# Linux (x86_64)
curl -LO https://github.com/conallob/jira-beads-sync/releases/latest/download/jira-beads-sync_Linux_x86_64.tar.gz
tar xzf jira-beads-sync_Linux_x86_64.tar.gz
sudo mv jira-beads-sync /usr/local/bin/go install github.com/conallob/jira-beads-sync/cmd/jira-beads-sync@latestMore options: See Getting Started Guide for all installation methods including Docker, DEB, and RPM packages.
jira-beads-sync configureYou'll need a Jira API token from https://id.atlassian.com/manage-profile/security/api-tokens
jira-beads-sync quickstart PROJ-123This fetches the issue and all its dependencies (subtasks, linked issues, parent issues).
bd list # List all issues
bd show proj-123 # Show details
bd update proj-123 --status in_progressjira-beads-sync syncπ Detailed Usage: See CLI Guide for all commands and options.
Enable natural language issue management:
claude --plugin-dir /path/to/jira-beads-syncThen simply ask Claude:
You: Import PROJ-123 from Jira
You: Show me all open issues
You: Mark PROJ-124 as in progress
You: Sync changes back to Jira
π Plugin Guide: See Plugin Guide for complete plugin documentation.
This tool uses Protocol Buffers internally for type-safe data handling:
Jira (JSON) β Protobuf β beads (YAML) β Protobuf β Jira (JSON)
β β β β β
Fetch Convert Render Detect Update
Learn more: See CLAUDE.md for detailed architecture and CONTRIBUTING.md for development setup.
Contributions welcome! See CONTRIBUTING.md for:
- Development setup
- Coding standards
- Testing guidelines
- Pull request process
- π Getting Started Guide - New user walkthrough
- π₯οΈ CLI Guide - Complete CLI reference
- π€ Plugin Guide - Claude Code plugin usage
- π‘ Examples - Real-world scenarios
- ποΈ CLAUDE.md - Architecture for developers
- π€ Contributing - Development guidelines
- Issues: https://github.com/conallob/jira-beads-sync/issues
- Discussions: https://github.com/conallob/jira-beads-sync/discussions
- Sponsor:
BSD-3-Clause - See LICENSE file for details.