Configuration¶

All configuration lives in _bmad/atlassian/module.yaml. This file is preserved across re-installs.

Project Settings¶

Variable	Description	Default
`project_name`	Your project name	Directory name
`user_name`	Your name for agent communication	`"Developer"`
`communication_language`	Language agents communicate in	`"English"`
`document_output_language`	Language for generated documents	`"English"`
`user_skill_level`	`beginner` / `intermediate` / `expert`	`"intermediate"`

Atlassian Cloud Settings¶

Variable	Description	Default
`atlassian_cloud_id`	Your Atlassian Cloud ID (UUID)	(discover via transition-discovery)

All Atlassian MCP tool calls require a cloudId parameter. This must be the site's UUID (e.g., c317c250-...), not the site URL. Run /bmad-atlassian-transition-discovery to auto-discover it, or call getAccessibleAtlassianResources manually. If left empty, agents will discover it on first use but this adds an extra API call to every session.

Jira Settings¶

Variable	Description	Default
`jira_project_key`	Your Jira project key (e.g., `PROJ`)	`"PROJ"`
`jira_board_id`	Your Jira Agile board ID	(discover via transition-discovery)

Confluence Settings¶

Variable	Description	Default
`confluence_space_key`	Your Confluence space key	Same as project key
`confluence_parent_page_id`	Parent page ID for BMAD pages	(root of space)

Status Transitions¶

Maps BMAD abstract statuses to your Jira project's specific transition IDs. Run /bmad-atlassian-transition-discovery to auto-discover these.

status_transitions:
  epic:
    backlog_to_in_progress: "21"    # Your transition ID
    in_progress_to_done: "31"       # Your transition ID
  story:
    backlog_to_ready_for_dev: "11"
    ready_for_dev_to_in_progress: "21"
    in_progress_to_review: "31"
    review_to_done: "41"
    review_to_in_progress: "51"     # For re-work after failed review

Warning

Transition IDs vary per Jira project. Never copy IDs from another project -- always run transition-discovery.

Optional Features¶

Variable	Description	Default
`enable_worklogs`	Log agent session duration as Jira worklogs	`"false"`
`default_assignee`	Auto-assign stories to this Jira user (email)	(disabled)

Time Tracking with Worklogs¶

When enable_worklogs is set to "true", the Dev agent logs implementation session duration as a Jira worklog entry on the story being implemented. The worklog captures the time spent coding, with a description summarizing what was done. This data feeds into sprint velocity calculations and capacity planning. Worklogs are added via addWorklogToJiraIssue with a timeSpent parameter (e.g., "2h", "45m").

Label Conventions¶

Variable	Description	Default
`agent_label_prefix`	Prefix for agent-applied labels	`"bmad-agent-"`
`lock_label`	Label for agent locking	`"agent-active"`

Git/GitHub Integration (Optional)¶

These settings are configured by running /bmad-atlassian-git-discovery. See the Git Integration Guide for details.

Variable	Description	Default
`git_enabled`	Enable/disable all git operations	`"false"`
`git_github_repo`	GitHub repo in `owner/repo` format	`""`
`git_default_branch`	Base branch for new feature branches	`"main"`
`git_branch_prefix`	Branch name prefix	`"{jira_project_key}"`
`git_commit_prefix`	Commit message prefix	`"feat({issue_key})"`
`git_auto_push`	Auto-push commits to remote	`"true"`
`git_auto_pr`	Auto-create PR on Review transition	`"true"`
`git_pr_draft`	Create PRs as drafts	`"true"`
`git_pr_auto_approve`	Auto-approve PR on review pass	`"true"`
`git_pr_auto_merge`	Auto-merge PR on approval (not recommended)	`"false"`