From jira-beads-sync
Sets up Jira API credentials interactively, via environment variables, or config file, enabling issue import. Verifies the connection and provides troubleshooting guidance.
How this command is triggered — by the user, by Claude, or both
Slash command
/jira-beads-sync:configure-jiraFiles this command reads when invoked
The summary Claude sees in its command listing — used to decide when to auto-load this command
Configure Jira credentials to enable importing issues from Jira. This is a one-time setup required before using the `import-jira` command. ## Configuration Methods Jira credentials can be configured in three ways (in order of precedence): ### 1. Interactive Configuration (Recommended) Run the interactive configuration command: This will prompt for: - **Jira Base URL**: The root URL of your Jira instance (e.g., `https://jira.example.com`) - **Username/Email**: Your Jira account email - **API Token**: A Jira API token (not your password) The configuration is saved to `~/.config/jira-be...
Configure Jira credentials to enable importing issues from Jira. This is a one-time setup required before using the import-jira command.
Jira credentials can be configured in three ways (in order of precedence):
Run the interactive configuration command:
jira-beads-sync configure
This will prompt for:
https://jira.example.com)The configuration is saved to ~/.config/jira-beads-sync/config.yml
Set these environment variables:
export JIRA_BASE_URL=https://jira.example.com
export [email protected]
export JIRA_API_TOKEN=your-api-token
Environment variables override the config file.
Manually create ~/.config/jira-beads-sync/config.yml:
jira:
base_url: https://jira.example.com
username: [email protected]
api_token: your-api-token
Security Note: API tokens should be treated like passwords. Never commit them to version control.
After configuration, test the connection by importing a known issue:
jira-beads-sync quickstart <test-issue-key>
If you see "invalid configuration" or authentication errors, run jira-beads-sync configure again.
User: Configure Jira credentials
Claude: I'll help you configure Jira credentials. This is stored securely in your home directory.
[Runs: jira-beads-sync configure]
Jira Configuration
==================
Jira Base URL (e.g., https://jira.example.com): https://company.atlassian.net
Jira Username/Email: [email protected]
Jira API Token: ************************
✓ Configuration saved successfully
Configuration is stored at: ~/.config/jira-beads-sync/config.yml
To get a Jira API token, visit:
https://id.atlassian.com/manage-profile/security/api-tokens
You can now use: import-jira <jira-url-or-key>
/browse/ or issue keys~/.config/jira-beads-sync/config.yml has restricted permissions (0600)npx claudepluginhub conallob/jira-beads-sync/jira-assistant-setupGuides conversational setup of JIRA Assistant Skills: checks prerequisites, installs jira-as package, collects credentials and API token, configures environment variables, validates connection.
/jira-importImports Jira issue or epic by creating local pm/issues or pm/epics directory with kebab-case name and displays details, summary, and acceptance criteria. For epics, prompts for bulk child import.
/f5-jiraManages unified Jira integration: setup connection, sync issues/files, check status, convert Excel/CSV, handle issues/attachments via subcommands.
/jiraManages Jira tickets: fetch and analyze requirements, add comments, transition status, or search issues with JQL.
/syncBi-directionally syncs local dev progress with Jira: pulls issue details/changes, pushes comments/status/PRs, detects/resolves conflicts, updates checkpoints.