Skip to main content
Mo reads Linear and Jira issues to scope a session, and you file confirmed bugs back from the finding.

Linear

Use Linear issues and acceptance criteria to scope Mo sessions. File a finding back to Linear with Create Linear issue on the bug.

Read issues during testing

Add Linear MCP through the MCP connection setup. Use these settings: For context without write tools, use https://mcp.linear.app/mcp/readonly. Linear also accepts an API key or OAuth token through an Authorization: Bearer <token> header. Review the connected account’s permissions and the tools listed by Test connection. Include the issue ID and app URL in your brief:
Connect Notion too if the brief needs a linked specification there. Specify whether Mo may create or update issues in your brief.

File bugs

Connect Linear in Settings > Integrations. In a Mo session’s bug report, open Create issue and choose Create Linear issue. Pick the team and edit the prefilled title and description before you create it. With Atlassian connected there, Create Jira issue files it in Jira. Filing is per bug: Accept only marks the bug accepted. Create issue also offers Create GitHub issue, which needs the Momentic GitHub App with Issues: write. See triage.

Jira

Give Mo Jira acceptance criteria and Confluence specifications through Atlassian Rovo MCP. Your connected account’s permissions determine which pages, issues, and tools Mo can access.

Connect Jira and Confluence

Add Atlassian Rovo MCP through the MCP connection setup: Sign in and grant access.

Test from an issue

Include the issue or document reference and your app’s URL in your brief:
Review the provider’s account requirements and permissions. Specify whether Mo may use tools that write data. The native Atlassian connection in Settings > Integrations files issues from repository test results and Mo bugs. Connect Rovo MCP to let Mo read Jira and Confluence during a session. If you can’t connect it, attach an exported spec or upload one and include its sandbox path.

Xray

To sync test cases or import execution results into Xray, contact support with the task, your Jira deployment type, and the report format you need. These tasks need different connections and configuration. Repository tests can export JUnit XML or JSON for a separate import step. These reporters write result files; they don’t create Jira issues or sync Xray test cases.