Jira

Before you start

Atlassian's hosted service prefers OAuth. It also accepts an API token, but only if an organisation admin has turned that on for the whole organisation. Worclaude signs in without a person present, which is the case that setting governs.

If your admin has not enabled it, this source cannot connect and there is nothing you can change here to fix it. Ask them to turn on API token access for Atlassian's Rovo integration. Their console may label it differently from one month to the next, so it is worth quoting "API token access" to them rather than a screen name.

Where to find the token

1. id.atlassian.com/manage-profile/security/api-tokens (your avatar → Manage account → Security → Create and manage API tokens).
2. Create API token, label it Worclaude, set an expiry.
3. Copy it now. Atlassian shows it once.

This is the same kind of token the Confluence source uses; you can reuse one token for both if you prefer fewer to rotate.

What it can see

Everything your Atlassian account can see, and nothing more. There is no way to narrow it to one project from this side. If you need that, ask your admin for a service account scoped to the projects in question and use its token here.