Artificial intelligence news.
Straight from the original announcements.

Mastra Factory adds Jira, GitLab and incident.io as work intakes

September 30, 2026Source: Mastra
Mastra Factory adds Jira, GitLab and incident.io as work intakes
Image: Mastra

Mastra Factory now supports three more intake sources: Jira, GitLab and incident.io. According to Mastra, the additions give teams more ways to manage and resolve issues, feature requests and incident follow-ups.

Key points
  • Mastra Factory now supports Jira, GitLab and incident.io as work intakes.
  • They join GitHub, Linear and Slack, which Factory supported at launch earlier this year.
  • The intake column can be filtered by source, and items can be moved through the pipeline until complete.
  • The providers ship in the @mastra/factory package and require version 0.16.0 or later.
  • Credentials are set in .env and configured under Settings → Work Intake in the Factory UI.

Three new sources join the intake lineup

Mastra launched Factory earlier this year with support for GitHub, Linear and Slack. The company followed that with a beta launch earlier this month. With the latest update, Jira, GitLab and incident.io are added to the list of places where work can come from.

The intake column in Factory can be filtered by source, so users can see where each issue originated. Opening an item shows the full issue description, and the item can then be moved through the pipeline until the work is complete. Mastra also points to a recent workshop, Build and Own Your Software Factory, for readers who want to learn more about the product.

How to set it up

Every intake provider ships as part of the @mastra/factory package, which is installed with npm install @mastra/factory@latest. Mastra notes that version 0.16.0 or later is required, and that the support was added in PR #20579, PR #23327 and PR #24604.

Credentials for each intake go into the project's .env file. Afterwards, the intakes are configured under Settings, then Work Intake, in the Factory UI. The variables listed in the source are:

  • GitLab: GITLAB_ACCESS_TOKEN and GITLAB_ACCESS_TOKEN_TYPE (the example uses the value personal)
  • Jira: JIRA_BASE_URL, JIRA_EMAIL and JIRA_API_TOKEN
  • incident.io: INCIDENT_IO_API_KEY

For the Jira base URL, Mastra's example uses an Atlassian-hosted address in the form https://your-team.atlassian.net.

What it means for teams

Teams that track work in Jira or GitLab, or that handle incident follow-ups in incident.io, can now bring those items into Factory alongside the sources it already supported. Because the intake column can be filtered by source, items from different tools can be reviewed in one place while still showing where each one came from.

Those who have not tried Factory yet can start with npm create factory@latest. Mastra also links to documentation pages for GitLab, Jira and incident.io, as well as pages on reviewing items and troubleshooting, for full configuration options.

Related news

Products and tools
Products and toolsNovember 9, 2026, 13:07

Samepage.ai launches Bets to coordinate AI-era product teams

Samepage.ai has launched Samepage Bets, a platform that brings product research, software development and go-to-market work onto one board. The company says human team…

Mastra launches program to build custom AI agent harnesses with companies
Products and toolsNovember 5, 2026

Mastra launches program to build custom AI agent harnesses with companies

Mastra has launched a Custom Harness Program that pairs forward-deployed engineers with company teams to build AI agent systems tailored to their goals, workflows and…

Mastra Adds TTFC and TTFT Metrics to Agent Observability
Products and toolsNovember 5, 2026

Mastra Adds TTFC and TTFT Metrics to Agent Observability

Mastra has added latency metrics for every agent and model call in its platform and Studio, allowing developers to track how long users wait for a response and how…