Jira Cloud connector

Ingest all of your Jira Cloud pages into Workplace Search.

The Jira Cloud Connector requires that you connect Workplace Search within Atlassian.net.

For self hosted Jira, see Jira Server.


You will need your Public Key from Workplace Search.

The Public Key will be provided to Jira for a secure connection between both applications. Copy it!

Login to Jira as an administrator.

You’ll need to access Application Links… But they’re hidden.

Reveal them by replacing [EXAMPLE] in the following with your own Jira URL:


Next, enter the host address for Workplace Search.

By default, the address is: http://localhost:3002.

Click Create new link:

Figure 45. Connecting Jira

It will fail… That’s okay. Everybody fails sometimes.

Confirm the link, then proceed.

We admit: this next part will feel strange. But the end result will securely connect the two applications.

A modal appears and within it we’ll need to enter some information:

Figure 46. Connecting Jira
  • Application Name: Elastic Workplace Search
  • Application Type: Generic Application
  • Service Provider Name: Elastic
  • Consumer key, Shared secret, Request Token URL, Access token URL, Authorize URL: Any random value. A . will do.
  • Create incoming link: Check this box.

Click Continue.

A final modal will appear:

Figure 47. Connecting Jira
  • Consumer Key: elastic_enterprise_search
  • Consumer Name: Elastic
  • Public Key: Your Public Key from Workplace Search.

Click Continue.

A successful affirmation appears…

Now, over to Workplace Search for the finishing touches.

Add your Base URL.

It is wherever Workplace Search can reach your Jira instance, such as https://example.atlassian.net/.

Finish the flow…​ Congratulations!

Jira Cloud is now a content source – it’s time to search.

You can now make the source available to various groups and scale its relevance priority.