Native Linear, Jira & GitHub Issues Bidirectional Integration
Native Linear, Jira & GitHub Issues Bidirectional Integration
Available since: v1.0.151
SaaS Factory supports native bidirectional integration with Linear, Jira, and GitHub Issues. Engineering teams can delegate implementation tasks to Droids directly from their existing issue tracker using @mentions, and receive traceable pull requests without leaving their workflow.
How It Works
1. @Mention Delegation
Inside any Linear issue, Jira ticket, or GitHub Issue, an engineer can @mention the configured Droid handle in a comment to delegate the task:
@factory-droid Please implement this according to the acceptance criteria above.
The Droid:
- Reads the issue title, description, and any linked context.
- Executes the task autonomously through the standard Factory pipeline.
- Opens a pull request in the connected repository.
2. Traceable Pull Requests
Every PR created via @mention delegation includes a back-reference to the originating issue:
- Linear: Links to the Linear issue URL and embeds the issue ID in the PR description.
- Jira: Embeds the Jira ticket key (e.g.
ENG-1234) and links to the ticket. - GitHub Issues: Links to the GitHub Issue number (e.g.
Closes #42) in the PR body.
This gives teams a complete audit trail across both the issue tracker and the repository.
3. Bidirectional Status Sync
| Event in Factory | Update in Issue Tracker |
|---|---|
| Droid picks up task | Issue moves to In Progress |
| PR opened | Issue updated with PR link |
| PR merged | Issue moved to Done / Closed |
| PR closed without merge | Issue status rolled back |
Supported Platforms
| Platform | @Mention Delegation | Traceable PRs | Status Sync |
|---|---|---|---|
| Linear | ✅ | ✅ | ✅ |
| Jira | ✅ | ✅ | ✅ |
| GitHub Issues | ✅ | ✅ | ✅ |
Important Limitations
No Automatic Inbound Task Routing
Issues created in Linear, Jira, or GitHub Issues are not automatically ingested into the SaaS Factory feature queue. The feature queue is SaaS Factory-native.
To add a task from an external tracker into the autonomous pipeline:
- Copy the task details into a new SaaS Factory feature entry manually.
- Or use @mention delegation directly on the external issue to trigger a one-off Droid execution without adding it to the feature queue.
Feature Queue Remains Authoritative
The SaaS Factory feature queue is the single source of truth for all scheduled, prioritised, and recurring autonomous work. External issue trackers are delegation surfaces — not pipeline inputs.
deals.ts Is Unrelated
The deals.ts schema and router manage SaaS Factory's own internal deal pipeline. They are not connected to or affected by the Linear, Jira, or GitHub Issues integration.
Use Cases
- Enterprise onboarding: Teams already using Linear or Jira can begin delegating to Droids without migrating their project management workflow.
- One-off implementation tasks: Engineers can hand off a well-defined ticket to a Droid and track progress directly in the issue tracker.
- Audit-ready delivery: Compliance-conscious teams get a full chain of custody from issue creation to merged PR.
What This Integration Does Not Replace
- SaaS Factory's autonomous feature discovery and beast mode supercycles.
- The native feature queue for managing the full autonomous roadmap.
- Any existing CI, release, or deployment workflows.