Search issue titles, descriptions, and metadata from selected Jira Cloud projects. Each teammate connects their own Jira account to search issues they can access.
Jira Search uses Member accounts; central indexing with a service account is not supported. Comments, attachment contents, dashboards, and saved filters are not indexed.
Before you start
- A Studio organization admin must approve Jira. The admin can configure the source, or the first member connection can supply its site and projects.
- Use a Cloud site hostname such as
your-team.atlassian.net. Server and Data Center are not supported. - Each person needs a verified Studio email matching their active Atlassian account's email, plus access to the selected site and projects. Jira's Browse Projects and issue security permissions determine the issues they can search.
On hosted Studio, teammates authorize Studio's existing app. Self-hosted deployments configure the shared OAuth app once.
Search uses read:jira-work, read:me, and offline_access for issues, identity, and refresh. Studio's shared Jira app also requests permissions for workflow actions, including writes and deletes. Review the consent screen before authorizing.
Add Jira projects
Choose Jira
Open Settings → Sources → Add source and select Jira. This opens Add Jira projects. To add another project selection later, open Jira from the Sources list and select Add projects.
Choose the projects
Under Account for browsing, select a saved account (including your personal Search account) or choose Connect Jira account. Enter Jira site, then choose Projects. All in the dropdown selects every project the account can currently browse; newly created projects are not added automatically. Clear the picker search before selecting all.
To enter keys such as ENG, SUPPORT manually, use the switch beside Projects; this works without a browsing account. Switching between the picker and manual entry keeps your selection.
Account for browsing only loads the project picker, using OAuth or Add service account. It does not enroll anyone for Search. A service account needs Jira access and the Jira read scopes; Confluence-only tokens do not work here.
Save the project selection
Under More options, optionally set a JQL Filter, such as status = "Done", and choose Metadata tags. Leave JQL empty for all accessible issues in the selected projects. Enter conditions only; omit ORDER BY because Studio supplies sorting.
Select Add projects. This saves the shared scope; it does not authorize accounts or send invitations.
Connect your search account
Open Integrations in the main sidebar and select Connect for Jira. In the new tab, authorize the configured site using the Atlassian email matching your verified Studio email.
Each teammate follows this step. Studio reuses an existing authorized account where possible. The Jira row shows your connection and indexing status, even when the organization has several project selections.
Connect before a source exists
After an admin approves Jira, a teammate can select Connect on the Jira row in Integrations. To add another site or project selection later, open the Jira row's actions menu (…) and select Add projects:
- Open Your account and select a saved account or Connect Jira account. Authorize using the Atlassian email matching your verified Studio email.
- Enter the hostname under Atlassian site, then choose Projects. Clear the picker search to use All, or use the arrows beside Projects to enter comma-separated keys. You can select up to 1,000 projects. Changing the account or site clears the project selection.
- Select Connect & Sync. Studio saves the selected scope and starts indexing with your account.
Manage project connections
Admins open Settings → Sources → Jira, then a connection’s Documents, Settings, or Sync history. Metadata tags include issue type, status, priority, labels, assignee, and last updated.
Teammates use the configured site and projects without entering them again. Additional connection required means another configured selection needs authorization; select Connect. Reconnect is for an account whose authorization needs renewing.
Invite teammates through Settings → Members → Invite or SSO, then have them connect Jira through Integrations. Settings → Sources → People, filter by Jira, then select Request connections only requests a provider connection; it does not invite people to the organization.
Studio checks Jira separately for each connected person. Content becomes searchable as indexing finishes; issue changes and lost access are reflected after later syncs.
Sync runs automatically; teammates do not need to start it. The Jira row's … → Disconnect action disconnects the selected account from every Jira connection in this organization, including workflows using that account. It asks for confirmation.
Troubleshooting
| Problem | What to check |
|---|---|
| No source setup controls | Ask a Studio organization admin to approve Jira. |
| Projects are empty or disabled | Enter the correct domain, connect a browsing account with project access, or switch to manual keys. |
| Connected, but no issues | Check the authorized site, project access, issue security, and JQL. An admin's Jira access does not grant access to teammates. |
| Projects appear but issues do not sync | Ask the Atlassian admin whether a data security policy blocks Studio from the selected projects. Project visibility does not prove that an app may read its issues. |
| Email mismatch | Use the Atlassian email matching your verified Studio email. If switching accounts fails, sign out of Atlassian and retry Connect. |
| Reconnect | Reauthorize and grant all requested permissions. A revoked grant or changed scope list can require a new connection. |
| Connection tab does not open | Allow pop-ups for Studio and retry. |
| Invalid callback URL | Ask the operator to check the app identified by JIRA_CLIENT_ID; its callback must exactly match Studio's redirect_uri. See operator setup below. |
Open a missing issue in Jira using the connected account. For company-managed projects, an admin can check Settings → System → Admin Helper → Permission Helper → Browse Projects, using the affected user and issue key. Resolve Jira access first, then sync again. See Atlassian's Permission Helper instructions.
Self-hosted operator setup
Configure one shared Jira OAuth app for the deployment:
- In the Atlassian developer console, select or create an OAuth 2.0 integration.
- Under Authorization → OAuth 2.0 (3LO), add
https://<your-studio-domain>/api/auth/oauth2/callback/jiraas a callback. - Under Permissions, add Jira API and configure the full
jirascope list from Studio's OAuth configuration, including its Jira Service Management and Assets scopes. Add User Identity API → read:me. Studio requestsoffline_accessfor refresh tokens; Search's three scopes above are only a subset of this shared app's permissions. - Enable sharing under Distribution. Set
JIRA_CLIENT_IDandJIRA_CLIENT_SECRETfrom the app's Settings, verifyNEXT_PUBLIC_APP_URL, and restart Studio. - Connect from Integrations and select the configured site. After changing the OAuth client or requested scopes, use Settings → Sources → More → Update sign-in settings, then have affected teammates reconnect.
The callback must match Studio's scheme, hostname, port, and path exactly. If only the app owner can connect, check Distribution. See the Atlassian OAuth guide and Studio deployment reference.