Jira

Jira supplies project issues to Factory boards. Connect a Jira Cloud site before selecting projects for intake. Each selected project also needs a destination Factory and board under the organization's routing settings.

Platform-backed servers use their Platform connection. Servers with their own Jira credentials can use the self-managed configuration.

Connect a site

You need a running Factory, a linked target repository, and permission to authorize the intended Jira site.

1. Open Settings → Work Intake.
2. Under Jira issues, select Connect Jira.
3. Authorize the intended site in Atlassian and return to Factory.
4. Confirm the connected site name and that projects are available.

Select Connect another site to add more sites. Projects from every connected site appear in the picker, grouped by site.

If the section says Jira isn't configured on the server, the server operator must enable a Platform-backed integration or configure a complete credential group.

Select projects and route issues

In Work Intake, enable Sync Jira issues and select the projects you want to follow. Projects are grouped by their Jira sites. Selections are shared: they feed every member's board.

Under Jira routing, choose the destination Factory and board for each selected project. Each Jira project supplies one board in one Factory. Choose Work for the built-in workflow. Until a project is routed, its issues aren't picked up.

Setting	Scope	Expected result
Site connection	Connected sites	Lists each site's available projects.
Sync and project selection	Organization	Factory imports active issues from the selected projects.
Jira routing	Organization	Each selected project has a destination Factory with the intended codebase and a selected board.

Route the project to a Factory linked to the repository where its issues should be implemented. Confirm the destination before changing shared routing for teammates.

Verify issue intake

1. Create one active issue in a selected, routed Jira project.
2. Return to the destination Factory's Work board.
3. Match the issue's Jira key, title, and source link.
4. Select Investigate and inspect the session's understanding of the issue.

Give synchronization time to run. Planning, implementation, and review then follow the Work workflow. When a linked Jira issue becomes completed or canceled, built-in rules can move its Work card to Done or Canceled. Those state changes are asynchronous.

A reconciliation worker refreshes the status and metadata of imported issues every five minutes by default, without needing an open browser. The event delivery variables adjust or disable it.

Agents working on Jira-sourced runs can read the issue and post comments back to Jira through built-in tools.

If issues don't appear in Factory, read Troubleshooting.

Use your own credentials

For a self-managed connection, create an API token at id.atlassian.com under Security → API tokens. The integration supports Jira Cloud sites and authenticates with the account email and token.

Set all three variables on the Factory Server and restart it:

.env

JIRA_BASE_URL=https://acme.atlassian.net
JIRA_EMAIL=you@example.com
JIRA_API_TOKEN=your-jira-api-token

The generated entry uses this explicit integration when all three values are present. A partial group disables direct Jira and logs a warning. The credentials are deployment-global: every member reads Jira through the same account, and there is no per-user authorization step. Project selection and routing still happen in Work Intake after the server is configured.