Synapse FAQ

What does Synapse do?

Inside Jira (Forge Issue Panel), Synapse generates requirements previews and test-ready artifacts from Jira issue context.

Synapse Forge runs on Atlassian using a Forge-native runtime with no external backend dependency.

What runs where?

• Atlassian Forge runtime: Jira app surface, scoped auth, and app workflow orchestration.
• External services: None for Synapse Forge app runtime.
• Jira Cloud: Source and destination for issue-linked artifacts.

Synapse Forge runs entirely in Atlassian-managed context.

How is data handled?

In Jira (Forge Issue Panel), Synapse Forge generates outputs from Jira issue context.

No external backend, no external storage, and no external network egress are used for the Forge runtime.

Jira credentials, personal access tokens, and shared secrets are not stored.

Jira permissions and sync behavior

• Access uses Forge appUserToken with scopes read:jira-work, write:jira-work, and read:app-user-token.
• Writes should be reviewed with your Jira permission model before production rollout.
• Sync actions are designed to be repeatable; validate idempotent behavior in your staging project for your configuration.

Runs on Atlassian

• Synapse Forge app runtime operates inside Atlassian Forge context.
• No external backend services, external storage, or shared secrets are required.
• Trust details: GitBook Trust & Security.

What are the limits?

LLM-assisted outputs can contain omissions or inaccuracies. Teams should treat outputs as drafts and apply human review before implementation or release decisions.

Roadmap disclaimer

Capabilities may change as Atlassian platform features and customer requirements evolve. Roadmap details are directional and not a delivery commitment.