ody task import

Synopsis

ody task import [--jira <ticket-or-url> | --github <issue-ref>] [--dry-run] [--verbose]

Flags

Exactly one source must be provided: use either --jira or --github.

Input Formats

Jira accepts:

• Full URL, for example https://company.atlassian.net/browse/PROJ-123
• Ticket key shorthand, for example PROJ-123

GitHub accepts:

• Full URL, for example https://github.com/owner/repo/issues/123
• Issue shorthand, for example owner/repo#123

Behavior

1. Validates input and enforces exactly one source (--jira or --github).
2. Resolves source input into a canonical ticket/issue reference.
3. Fetches issue data from Jira or GitHub.
4. Converts the fetched issue into task import prompt content.
5. Runs the configured backend agent to generate a .code-task.md file.
6. Writes the generated task into .ody/tasks/.

Dry run

Use --dry-run to print the generated import prompt without invoking the backend agent:

ody task import --jira PROJ-123 --dry-run

Authentication

Credentials must already be configured before importing tasks. Set up your provider profiles with ody auth, then run ody task import.

Example

Import from Jira using a ticket key:

ody task import --jira PROJ-123

Import from Jira using a full ticket URL:

ody task import --jira https://company.atlassian.net/browse/PROJ-123

Import from GitHub using shorthand:

ody task import --github owner/repo#123

Import from GitHub using a full issue URL:

ody task import --github https://github.com/owner/repo/issues/123

Preview without running the agent:

ody task import --github owner/repo#123 --dry-run

Stream backend output:

ody task import --jira PROJ-123 --verbose

Related

• ody plan -- Create new task plans
• ody task list -- View pending task files
• ody task edit -- Edit an existing task plan
• ody run -- Execute pending tasks with the agent loop