Skip to main content
Generated from bd help --doc jira. Synchronize issues between beads and Jira. Configuration: bd config set jira.url “https://company.atlassian.net” bd config set jira.project “PROJ” bd config set jira.projects “PROJ1,PROJ2” # Multiple projects bd config set jira.api_token “YOUR_TOKEN” bd config set jira.username “your_email@company.com” # For Jira Cloud bd config set jira.push_prefix “hippo” # Only push hippo-* issues to Jira bd config set jira.push_prefix “proj1,proj2” # Multiple prefixes (comma-separated) Environment variables (alternative to config): JIRA_API_TOKEN - Jira API token JIRA_USERNAME - Jira username/email JIRA_PROJECTS - Comma-separated project keys Examples: bd jira sync —pull # Import issues from Jira bd jira sync —push # Export issues to Jira bd jira sync # Bidirectional sync (pull then push) bd jira sync —dry-run # Preview sync without changes bd jira status # Show sync status

​
bd jira pull

Pull one or more items from Jira. Accepts bead IDs or external references as positional arguments. Equivalent to: bd jira sync —pull —issues <refs>
Flags:

​
bd jira push

Push one or more beads issues to Jira. Accepts bead IDs as positional arguments. Equivalent to: bd jira sync —push —issues <ids>
Flags:

​
bd jira status

Show the current Jira sync status, including:
  • Last sync timestamp
  • Configuration status
  • Number of issues with Jira links
  • Issues pending push (no external_ref)

​
bd jira sync

Synchronize issues between beads and Jira. Modes: —pull Import issues from Jira into beads —push Export issues from beads to Jira (no flags) Bidirectional sync: pull then push, with conflict resolution Conflict Resolution: By default, newer timestamp wins. Override with: —prefer-local Always prefer local beads version —prefer-jira Always prefer Jira version Examples: bd jira sync —pull # Import from Jira bd jira sync —push —create-only # Push new issues only bd jira sync —dry-run # Preview without changes bd jira sync —prefer-local # Bidirectional, local wins
Flags: