Connections

Jira / Atlassian

Camper manages Atlassian Teams (org-scoped) so team membership can track your org chart.

Connect with Atlassian (recommended)

  1. Open ConnectionsJira.
  2. Enter your Atlassian organization id (Admin → organization → Settings). This is not a secret.
  3. Click Connect with Atlassian and approve as an org admin.
  4. Camper seals a refresh token, discovers site host from accessible resources, and health-checks Teams list/get.

No personal API tokens are pasted on this path.

Advanced: API token

Use Advanced when OAuth is unavailable:

  • Email + Atlassian API token, or a bearer access token
  • Same organization id

Existing API-token connections keep working until you reconnect via OAuth.

Membership

Camper adds and removes people on Atlassian Teams using org-scoped membership APIs. Identity email is resolved to an Atlassian accountId via Jira user search (needs site host or cloud id on the connection — OAuth discovery usually fills this in).

If a person cannot be found in Jira (or privacy settings hide them), Camper records drift rather than failing the whole reconcile batch.

Bulk member adds can succeed for some people and fail for others in a single API response. Camper maps those outcomes per person (already a member → no-op, not found → drift-style failure, permission → surfaced) so one bad account does not fail everyone else in the batch.

Related

  • Setup for developers: repo docs/jira-oauth-setup.md
  • Issue #112 (OAuth), #41 (membership), #42 (partial bulk add)