Skip to main content
Connections is an enterprise feature. An open build has no Connections tab.
A Jira source is one project, added on Context like any other source. It reads through the workspace’s Atlassian connection, and one connection can serve several projects.

​
Connect the site

Jira reads through the workspace’s Atlassian connection: the site URL, an account email and an API token, made once in Settings › Connections and shared with Confluence. See Connections for where each value comes from. The account needs browse access to the projects you will add.

​
Add a project as a source

Press Add context on any Context page. Once the site is connected, Jira is offered among the connected accounts.
1

Scope

Enter the Project key, the prefix of the project’s issue keys: if issues look like KAN-42, the key is KAN. It is also the Key column under Projects and the segment after /projects/ in the project’s URL.The default scope is every standard issue of the project, in every status. Epics, stories, tasks and bugs are all read; a shipped story is still part of your specification. Sub-tasks are excluded. You do not need to pre-filter: tickets without specification content (bug reports, dependency bumps, chores) are set aside by the Document scan, where you can override any call.To narrow the scope anyway, enter a JQL filter. It is combined with the project scope for you, so write only the condition:
Do not include project = … or ORDER BY.
2

Check, then add

Check counts the issues the scope yields and lists the first few, storing nothing. A wrong project key surfaces here as The value ‘X’ does not exist for the field ‘project’. Then press Add and sync.
The source is titled after the project and syncs like a documentation site: when it is added, on Sync now, and once a day. Issues are fetched a hundred at a time, and Jira’s rate limits are honored, so a large project is a handful of requests.

​
What an issue becomes

One issue is one document, titled KEY: summary, with the description as its body and a deep link back to Jira. Ahead of the body the document states what Jira knows about the issue: The scan reads these. A workflow status TrueCourse has never seen classifies by its category, so a custom Ready for QA still counts as planned and Won’t Do stays out of scope. When two documents disagree, the scan knows which is newer and whether the older statement was delivered, dropped or superseded, and only a live disagreement becomes a conflict for you to settle. A comment, a label change or an assignee change does not re-curate an issue. Only its text does.

​
Not read

Comments, attachments, linked issues and custom fields are not part of the document. Jira Server and Data Center are not supported; the connection is Jira Cloud with an API token.