19  Jira Connector

Use this guide for the customer Jira connector. The standard customer path uses a Jira account and API token. It indexes issues and supported project data.

19.1 What is indexed or searched live

Nous indexes Jira issues, comments, project metadata, and supported issue fields that the configured Jira account can read. Use a project scope or JQL to limit the data.

19.2 Administrator role and authentication

The customer creates the Jira API token. Use a dedicated Atlassian service account with Browse Projects permission for every project to index. A Jira administrator should create or review the account and project permissions.

The API token is the current customer setup path. Do not use a Jira OAuth grant for this customer connector. Keep the token secret and rotate it in Atlassian.

19.3 Provider setup and permissions

Create an Atlassian account for indexing, grant it only the required Jira project permissions, and create an API token in the account security settings. Use the Jira Cloud base URL, for example https://example.atlassian.net.

19.4 Setup form fields

Field What to enter
Name A unique workspace connector name.
Jira Base URL The Jira site base URL without a project path.
Jira User Email Email for the Atlassian indexing account.
Jira API Token API token created for that account.
Using scoped token Turn on only for a scoped Jira API token.
How Should We Index Your Jira? Choose Everything, Project, or JQL Query.
Project Key The key when Project is selected, for example PROJ.
JQL Query A query for the issues to index. Do not use time filters or ORDER BY.
Comment Email Blacklist Optional email addresses whose comments should not be indexed.
Who has access Choose Everyone in the workspace or Specific Teams.

19.5 Workspace and Team access

Jira permissions control what the API account can read. Nous access controls who can search the indexed result. Use Specific Teams for a limited audience. Portal manages Team membership. A Team share cannot grant access to an issue outside the API account’s Jira permissions.

19.6 Test the connection

  1. Save the connector and wait for source sync and search indexing.
  2. Open a known issue as the API account and note its key.
  3. Search for the issue key and a phrase from its description.
  4. Confirm that comments and fields expected by the selected scope appear.
  5. Test access with the intended Workspace or Team members.

19.7 Common errors

Error Action
Authentication fails Check the Jira user email, API token, and site URL. Create a new token if the old one was revoked.
Project is empty Grant the API account Browse Projects and issue access.
JQL setup fails Remove time filters and ORDER BY, then validate the query in Jira.
Comments include unwanted users Add their exact email addresses to Comment Email Blacklist.

19.8 Reconnect, rotate, and remove

Rotate the API token in Atlassian, save the replacement in the connector, and run a test search before revoking the old token. Recreate the connector when you need to change its permanent access mode. Before removal, check document sets, agents, and Team shares.

19.9 Official provider documentation