> ## Documentation Index > Fetch the complete documentation index at: https://docs.argalabs.com/llms.txt > Use this file to discover all available pages before exploring further. # Atlassian > Atlassian Scenario seeding parameters, nested fields, and examples 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](https://docs.argalabs.com/api-reference/post-create-a-scenario.md). You can also import it with `arga test-runner scenarios import --file scenario.json`. ```json theme={null} { "name": "Atlassian eval fixture", "twins": [ "atlassian" ], "seed_config": { "atlassian": { "projects": [ { "key": "DEMO", "name": "Demo Project", "description": "Project description", "projectTypeKey": "software", "issues": [ { "summary": "Issue summary", "description": "Issue description", "issuetype": "Task", "priority": "High", "status": "In Progress", "labels": [ "backend" ], "assignee": "scenario-user-001", "comments": [ { "body": "Comment body" } ], "worklogs": [ { "timeSpent": "2h", "comment": "Worklog note" } ] } ] } ], "webhooks": [ { "url": "https://app.example.test/jira-webhook", "events": [ "jira:issue_created", "jira:issue_updated" ], "jqlFilter": "project = DEMO" } ], "service_desks": [ { "id": "1", "project_key": "HELP", "project_name": "IT Help Desk", "request_types": [ { "id": "1", "name": "Get IT help", "description": "Request help from IT", "issue_type_id": "10001" } ], "queues": [ { "id": "1", "name": "All open requests" } ], "requests": [ { "request_type_id": "1", "summary": "Laptop will not start", "description": "The power light flashes twice", "participants": [ "scenario-user-001" ] } ] } ], "organizations": [ { "name": "Acme", "account_ids": [ "scenario-user-001" ] } ], "software": { "boards": [ { "name": "Demo delivery board", "type": "scrum", "project_key": "DEMO", "sprints": [ { "name": "Sprint 1", "goal": "Ship the integration", "move_project_issues": true } ] } ] }, "confluence": { "spaces": [ { "key": "ENG", "name": "Engineering", "pages": [ { "title": "Runbook", "body": "

Operational guidance

", "labels": [ "runbook" ] } ] } ] } } } } ``` ## 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. | Parameter | Type | Description | | - | - | - | | `projects` | `object[]` | Projects fixtures in provider-native format. | | `webhooks` | `object[]` | Webhook subscriptions or configurations. | | `service_desks` | `object[]` | Service desks fixtures in provider-native format. | | `organizations` | `object[]` | Organizations fixtures in provider-native format. | | `software` | `object` | Software. | | `confluence` | `object` | Confluence. | ## 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[]` | Parameter | Type | Description | | - | - | - | | `key` | `string` | Key. | | `name` | `string` | Human-readable name. | | `description` | `string` | Description. | | `projectTypeKey` | `string` | ProjectTypeKey. | | `issues` | `object[]` | Issues fixtures in provider-native format. | ### `projects[].issues[]` | Parameter | Type | Description | | - | - | - | | `summary` | `string` | Summary. | | `description` | `string` | Description. | | `issuetype` | `string` | Issuetype. | | `priority` | `string` | Priority. | | `status` | `string` | Status. | | `labels` | `string[]` | Custom label names or objects containing name. | | `assignee` | `string` | Assignee. | | `comments` | `object[]` | Comments fixtures in provider-native format. | | `worklogs` | `object[]` | Worklogs fixtures in provider-native format. | ### `projects[].issues[].comments[]` | Parameter | Type | Description | | - | - | - | | `body` | `string` | Text content. | ### `projects[].issues[].worklogs[]` | Parameter | Type | Description | | - | - | - | | `timeSpent` | `string` | TimeSpent. | | `comment` | `string` | Comment. | ### `webhooks[]` | Parameter | Type | Description | | - | - | - | | `url` | `string` | Url. | | `events` | `string[]` | Events fixtures in provider-native format. | | `jqlFilter` | `string` | JqlFilter. | ### `service_desks[]` | Parameter | Type | Description | | - | - | - | | `id` | `string` | Explicit resource identifier, when supported. | | `project_key` | `string` | Project key. | | `project_name` | `string` | Project name. | | `request_types` | `object[]` | Request types fixtures in provider-native format. | | `queues` | `object[]` | Queues fixtures in provider-native format. | | `requests` | `object[]` | Requests fixtures in provider-native format. | ### `service_desks[].request_types[]` | Parameter | Type | Description | | - | - | - | | `id` | `string` | Explicit resource identifier, when supported. | | `name` | `string` | Human-readable name. | | `description` | `string` | Description. | | `issue_type_id` | `string` | Issue type id. | ### `service_desks[].queues[]` | Parameter | Type | Description | | - | - | - | | `id` | `string` | Explicit resource identifier, when supported. | | `name` | `string` | Human-readable name. | ### `service_desks[].requests[]` | Parameter | Type | Description | | - | - | - | | `request_type_id` | `string` | Request type id. | | `summary` | `string` | Summary. | | `description` | `string` | Description. | | `participants` | `string[]` | Participants fixtures in provider-native format. | ### `organizations[]` | Parameter | Type | Description | | - | - | - | | `name` | `string` | Human-readable name. | | `account_ids` | `string[]` | Account ids fixtures in provider-native format. | ## 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](https://docs.argalabs.com/twins/seeding.md) for saving, provisioning, and resetting fixtures. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.