Connect Jira so Coworker can see what your teams are working on. Jira needs a workspace credential from an admin — individual connections cannot replace it.
What Coworker can do with Jira
Index projects, issues, comments and issue history
Produce one report per project with activity: issues created, progressed and resolved, who drove them, and notable discussion from comments. Quiet projects produce nothing.
Read and act on tickets during Deep Work — including creating and updating issues when a task explicitly requires it
Each report inherits the project's access policy, so its audience matches who can see the project in Jira.
Before you start
An admin must connect Jira for the workspace. Until they do, a Jira connection syncs nothing at all, no matter how many members have connected their own accounts.
The admin needs the Jira base URL, plus one of three accepted credential shapes.
Connect as an admin
Open Data Sources from the admin settings in Coworker and select Jira.
Enter your Jira base URL and one of the following:
Preferred: a tenant API token used with an Atlassian email — it addresses your tenant directly
A scoped token used with a Cloud ID
A service-account token (accepted as a fallback, but it may be throttled)
Save. The URL, email, token and Cloud ID must form a consistent set.
Connect as a member
Go to the Work page and click Data Sources.
Select Jira and complete the OAuth authorization.
Your individual connection does not drive indexing. It repairs identity that Atlassian's admin APIs withhold, and lets Coworker act in Jira as you.
Good to know
Jira and Confluence are connected together via the Atlassian OAuth flow.