slug: atlassian provider: Atlassian generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Banking & Capital Markets - Software & Technology min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 16 edges: - tag: Commits spec_file: atlassian-commits-api-openapi.yml capability_id: BC-4200.40 capability_id_l1: BC-4200 capability_name: Software Construction Management confidence: 0.85 evidence: '''Approve A Commit'', ''Create Comment For A Commit'', ''List Commits'', schema commit_comment' reason: Git commit listing, approval and inline commenting are source control and code review practice — Software Construction Management. - tag: Deployments spec_file: atlassian-deployments-api-openapi.yml capability_id: BC-4210 capability_id_l1: BC-4210 capability_name: Software Release & Deployment Management confidence: 0.85 evidence: GET /repositories/{workspace}/{repo_slug}/deployments "Atlassian List Deployments"; POST .../environments "Atlassian Create An Environment"; schemas deployment_state, deployment_environment, deployment_release reason: Bitbucket surface for tracking software deployments and the environments they target, plus deploy keys — this is software release & deployment management. Operations span both deployment records and environment lifecycle, so no single L2 is named cleanly (deployment orchestration vs environment management), hence L1 only. - tag: Pipelines spec_file: atlassian-pipelines-api-openapi.yml capability_id: BC-4210.10 capability_id_l1: BC-4210 capability_name: Continuous Integration Management confidence: 0.85 evidence: '''Atlassian Run A Pipeline'', ''Atlassian List Steps For A Pipeline'', ''Atlassian List Caches''; schemas pipeline_step_state, pipeline_schedule_post_request_body' reason: Bitbucket Pipelines executes CI build pipelines with steps, caches and schedules against a repository — Continuous Integration Management. Deployment environment variables also touch configuration/secrets, hence not full confidence on the sub-capability. - tag: Pullrequests spec_file: atlassian-pull-requests-api-openapi.yml reanchored_from: atlassian-pullrequests-api-openapi.yml capability_id: BC-4200.40 capability_id_l1: BC-4200 capability_name: Software Construction Management confidence: 0.85 evidence: '"Atlassian Create A Pull Request", "Atlassian List Default Reviewers", schemas "pullrequest", "pullrequest_merge_parameters", "pullrequest_comment"' reason: Pull request creation, review assignment, comments and merge are exactly the code review and source-control collaboration disciplines of Software Construction Management. - tag: Source - Repositories spec_file: atlassian-source-repositories-api-openapi.yml capability_id: BC-4200.40 capability_id_l1: BC-4200 capability_name: Software Construction Management confidence: 0.82 evidence: POST /repositories/{workspace}/{repo_slug}/src Atlassian Create A Commit By Uploading A File; GET .../filehistory/{commit}/{path} Atlassian List Commits That Modified A File reason: Operations read and write source files and commits in a Git repository — source control and implementation practice, i.e. Software Construction Management. - tag: Branch Restrictions spec_file: atlassian-branch-restrictions-api-openapi.yml capability_id: BC-4200.40 capability_id_l1: BC-4200 capability_name: Software Construction Management confidence: 0.8 evidence: '''Create A Branch Restriction Rule'' on /repositories/{workspace}/{repo_slug}/branch-restrictions, schema branchrestriction' reason: Source-control branch permission rules govern code contribution and review discipline in a Git repository — Software Construction Management. - tag: Commit Statuses spec_file: atlassian-commit-statuses-api-openapi.yml capability_id: BC-4210.10 capability_id_l1: BC-4210 capability_name: Continuous Integration Management confidence: 0.8 evidence: '''Create A Build Status For A Commit'' at /commit/{commit}/statuses/build, schema commitstatus' reason: Build status reporting against commits is CI pipeline signalling — Continuous Integration Management. - tag: Repositories spec_file: atlassian-repositories-api-openapi.yml capability_id: BC-4200.40 capability_id_l1: BC-4200 capability_name: Software Construction Management confidence: 0.8 evidence: '"Atlassian Create A Repository", "Atlassian Fork A Repository", "Atlassian List Explicit Group Permissions For A Repository"' reason: Source code repository lifecycle, forking and repository-level access configuration is the source-control substrate of Software Construction Management. - tag: Users spec_file: atlassian-users-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.8 evidence: POST /v2/orgs/{orgId}/users/invite 'Invite Users to Organization'; 'Suspend User Access'; 'Restore User Access'; 'Grant User Product Access'; 'Revoke User Product Access'; 'Assign Organization-level Role' reason: Atlassian admin API performs org-level user account lifecycle, suspension/restore and product/role grant-revoke across directories — classic identity and access administration (joiners-movers-leavers, entitlement grants). - tag: Groups spec_file: atlassian-groups-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.75 evidence: POST /rest/api/3/group "Atlassian Create Group"; POST /rest/api/3/group/user "Atlassian Add User To Group"; DELETE /rest/api/3/group/user "Atlassian Remove User From Group"; GET /v1/orgs/{orgId}/groups reason: Group lifecycle and user-to-group assignment across the Atlassian org admin and Jira APIs — the access-grouping mechanism for product entitlement and permissions, which is identity and access management. Schemas (UpdateUserToGroupBean, GroupDetails, UserDetails) confirm access-control rather than HR semantics. - tag: Permission Schemes spec_file: atlassian-permission-schemes-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.75 evidence: '''Atlassian Create Permission Scheme'', ''Atlassian Get Permission Scheme Grants'', ''Atlassian Create Permission Grant''; schemas PermissionGrant, PermissionHolder' reason: Operations define and grant access rights to projects via permission schemes — authorisation administration, which sits under Identity & Access Management. Some ambiguity as it is application-internal configuration. - tag: Permissions spec_file: atlassian-permissions-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.72 evidence: '''Atlassian Get My Permissions'', ''Atlassian Get Bulk Permissions'', ''Atlassian Get Permitted Projects''; schema UserPermission' reason: Runtime evaluation of which permissions a user holds — access-rights checking, an IAM function. Confidence moderated because it is a read-only entitlement check embedded in the product. - tag: Branching Model spec_file: atlassian-branching-model-api-openapi.yml capability_id: BC-4210.30 capability_id_l1: BC-4210 capability_name: Release Engineering Management confidence: 0.7 evidence: '''Get The Branching Model Config For A Repository'', schema branching_model_settings' reason: Branching model configuration is branching/versioning discipline; closest fit is Release Engineering Management, though it also touches source-control practice (BC-4200.40), hence moderate confidence. - tag: Group spec_file: atlassian-group-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.7 evidence: POST /wiki/rest/api/group "Atlassian Create New User Group"; POST /wiki/rest/api/group/userByGroupId "Atlassian Add Member To Group By Groupid"; DELETE "Atlassian Remove Member From Group Using Group Id" reason: 'Creation and deletion of user groups and management of group membership in Confluence — the standard grouping construct used to grant product access and permissions, i.e. identity and access administration. Not HR group/organisation management: the objects are Group and user accounts, not employees.' - tag: Issues spec_file: atlassian-issues-api-openapi.yml capability_id: BC-900.30 capability_id_l1: BC-900 capability_name: Project Management confidence: 0.7 evidence: Atlassian Create Issue; Atlassian Edit Issue; Atlassian Bulk Create Issue; Atlassian Archive Issue S By Jql reason: Core Jira issue CRUD is the work-item tracking surface of a project tracking tool, matching Project Management (execution, planning, tracking). Some ambiguity because issues also serve defect/ITSM use cases. - tag: Refs spec_file: atlassian-refs-api-openapi.yml capability_id: BC-4200.40 capability_id_l1: BC-4200 capability_name: Software Construction Management confidence: 0.7 evidence: '"Atlassian List Branches And Tags", "Atlassian Create A Branch", "Atlassian Create A Tag"' reason: Branch and tag lifecycle in a Git repository is source-control practice under Software Construction Management; some overlap with release engineering's branching/versioning discipline.