Import from Jira and Confluence

Instead of uploading requirement docs by hand, you can connect an Atlassian Cloud site to a Knowledge Base. Play imports selected Jira issues and Confluence pages as evidence, so blueprints and test generation can work from the stories and specs your team already writes.

This currently supports Atlassian Cloud (your-company.atlassian.net). Play only ever reads Jira and Confluence - it never creates, updates, or deletes issues or pages.

What this feature does

  • Connects one Atlassian Cloud site to Play using an API token you provide

  • Imports chosen Jira issues (stories, tasks, and bugs) as Knowledge Base evidence

  • Imports chosen Confluence pages as Knowledge Base evidence

  • Lets you resync selected items later when the source content has changed

Before you start

You need a connector, which holds the credential Play uses to read your Jira projects and Confluence spaces. A connector is set up once per team by a team admin, and then anyone with access to the team's Knowledge Bases can import from it.

You'll also need:

  • An Atlassian Cloud site hostname, for example your-company.atlassian.net (without https://)

  • The email address you use to sign in to Atlassian

  • An Atlassian API token with access to the Jira projects and Confluence spaces you want to import. Create one at id.atlassian.com → Security → API tokens

The token is stored encrypted and is never shown again - only the last four characters are displayed so you can recognise it.

Play does not write back to Jira or Confluence. The token only needs permission to read the projects and spaces you import.

Set up a connector (team admins)

You can create the connector from either place:

  • Team Settings → Atlassian → + New connector

  • A Knowledge Base → Sources → + New connector (choose provider Atlassian)

Then:

  1. Enter a Name (for example My Atlassian connector).

  2. Enter the Site URL - the Cloud hostname only, such as your-company.atlassian.net.

  3. Enter your Atlassian account email.

  4. Paste the API token.

  5. (Recommended) Set a Default Jira project key and a Default Confluence space key. After the site, email, and token are filled in, Play loads matching projects and spaces so you can search and pick them.

  6. Select Test connection (Team Settings) or Connect (Knowledge Base modal) to confirm the token works, then save.

The connector now appears in the team's Atlassian list and can be reused for any Knowledge Base in that team.

Imports use the connector's default project and space. If those keys are missing, set them in Team Settings → Atlassian → Edit before you import.

Import Jira issues into a Knowledge Base

  1. Open the Knowledge Base and go to the Sources tab.

  2. Select Import from connection (or Add new connection if you have none yet), then choose a Jira connector.

  3. In Import Jira issues, confirm the connector. Issue search uses that connector's default project.

  4. Keep the issue types you want: Story, Task, and Bug.

  5. Search in Basic (ticket number or description) or JQL (for example status = "In Progress").

  6. Select up to 25 issues, then select Import.

  7. Follow the status as it moves from queued to syncing to completed. The imported issues then appear as a source in the Knowledge Base.

You can add more issues later with Configure import / Add Jira import. Extra issues for the same connector and project are merged into the existing import. There's a limit on how many Jira imports a single Knowledge Base can hold (5 by default); once you reach it, disconnect one to free a slot.

Import Confluence pages into a Knowledge Base

  1. Open the Knowledge Base and go to the Sources tab.

  2. Select Import from connection, then choose a Confluence connector.

  3. In Import Confluence pages, confirm the connector. Page search uses that connector's default space.

  4. Search pages in the space and select up to 5 pages.

  5. Select Import.

  6. Follow the status as it moves from queued to syncing to completed. The imported pages then appear as a source in the Knowledge Base.

You can add more pages later with Configure import / Add Confluence import. There's a limit on how many Confluence imports a single Knowledge Base can hold (5 by default); once you reach it, disconnect one to free a slot.

Keep the Knowledge Base in sync

Jira and Confluence imports do not auto-sync. When source content changes, update it yourself:

  • Resync selected - re-import the issues or pages you pick. Unchanged items are skipped.

  • Retry - run again if the last import failed. Previously imported content is left untouched when a sync fails.

If the Knowledge Base already has a usable blueprint, add, resync, and delete go through a change review. Live Knowledge Base content stays unchanged until you Apply Changes or Reject.

What gets imported - and what doesn't

Jira issues are imported as markdown evidence, including:

  • Summary, key, issue type, status, priority, environment, labels, and components

  • Description

  • Extra sections when those custom fields exist: Acceptance Criteria, Technical, Environment

Comments, attachments, worklogs, subtasks, issue links, votes, watches, assignee, and reporter are not imported.

Confluence pages are imported as markdown from the page body (title plus content). Attachments and comments are not imported as separate evidence.

Anything that is imported becomes searchable evidence in the Knowledge Base. Treat connected Jira issues and Confluence pages as readable by anyone with access to that Knowledge Base.

Change or remove an import

  • Select Disconnect on a Jira or Confluence source to remove that import from the Knowledge Base. You can choose Keep imported assets if you want the already-imported evidence to stay.

  • Deleting the connector in Team Settings also removes connected Confluence imports.

  • Use Configure import to add more issues or pages to an existing connection.

Troubleshooting

  • I don't see Import from Jira / Confluence or Team Settings → Atlassian. The feature may not be enabled for your team yet - ask your administrator.

  • Only Atlassian Cloud sites (*.atlassian.net) are supported. Server, Data Center, and custom hosts are not.

  • No default Jira project key / Confluence space key on this connector. Edit the connector in Team Settings → Atlassian and set the default keys. Imports search that project or space.

  • Connection failed / unable to access Jira or Confluence. Check the site hostname, account email, and API token. The token must belong to that email and have access to the site.

  • Jira advanced search is not valid. The JQL box uses Jira's search language. If Play says the search is not valid, fix the query syntax and try again.

  • The import shows failed. The specific reason is shown on the import. Check the connector token and that the issues or pages still exist. Previously imported content is left untouched.

  • I already have the maximum number of imports. Disconnect one Jira or Confluence import to free a slot (5 of each per Knowledge Base by default).