Skip to main content
Use atlassian in twins and put this configuration under seed_config.atlassian. Atlassian Cloud workspace with Jira projects/issues, Jira Service Management service desks and customer requests, Confluence spaces/pages, comments, labels, organizations, and webhooks.

Example seed

This is the complete Scenario request body for creating a Scenario. You can also import it with arga test-runner scenarios import --file scenario.json.

Parameters

The following fields belong directly inside seed_config.atlassian. Required nested fields are marked in their tables. Provider-native objects can contain service-specific fields beyond the representative record shapes below.

Resource fields

These tables describe the record shapes used by the example. Keep native field names and casing. Map keys such as property names, IDs, and metadata keys are supplied by your fixture.

projects[]

projects[].issues[]

projects[].issues[].comments[]

projects[].issues[].worklogs[]

webhooks[]

service_desks[]

service_desks[].request_types[]

service_desks[].queues[]

service_desks[].requests[]

organizations[]

API coverage and limitations

Twin name: atlassian (jira is an alias) Supports
  • Jira Cloud REST API v3 issue flows: create, read, update, delete, bulk create, transitions, changelog, edit metadata, comments, worklogs, attachments, issue links, properties, votes, watchers, and search/JQL.
  • Projects, users, components, versions, remote links, filters, dashboards, groups, fields, priorities, resolutions, statuses, status categories, issue types, server info, attachment metadata, and webhooks.
  • Jira Software Agile endpoints for boards, sprints, board sprints, and backlog issue moves.
  • OAuth 2.0 authorization code grant, scope enforcement, deterministic seeding, ADF storage for descriptions/comments, and HMAC-signed webhook delivery.
Known limitations
  • The v2 and latest REST aliases route to the v3-compatible implementation; exact historical differences between Jira API versions are not the fidelity target.
  • Plain-string descriptions and comments are auto-wrapped in a minimal Atlassian Document Format document.
  • Complex JQL behavior is modeled for deterministic testing, but edge cases outside the supported parser may return structured validation errors.
MCP tools: get_twin_catalog, provision_twins, start_url_validation, get_validation_results. See Scenario seeding for saving, provisioning, and resetting fixtures.