Connect Your Jira Account

Connect your Jira Cloud workspace to Continuum to manage issues, tasks, and sprints directly from Slack.

Before You Begin

Requirements:

  • Continuum installed in Slack (see Installing to Slack)
  • Jira Cloud account (Jira Server/Data Center not supported yet)
  • Admin or user access to the Jira workspace you want to connect

Note: Continuum currently supports Jira Cloud only. Jira Server/Data Center support coming soon.

Connection Methods

Method 1: Setup Page (Recommended)

  1. Open setup page - After installing Continuum, you'll be on the setup page. Or visit: https://continuumworks.app/setup?workspace_id={your_uuid}
  2. Click "Connect Jira" - Find the Jira integration card and click the "Connect Jira" button
  3. Authorize in Atlassian - You'll be redirected to Atlassian's authorization page. Select your Jira site/workspace and review permissions, then click "Authorize"
  4. Confirm connection - You'll be redirected back with ?jira_connected=true. Check Slack for a confirmation notification

Method 2: Slack Command

  1. Open Slack - In any channel or DM
  2. Run the command - Type: 
    /connect-jira
  3. Click the button - Slack will show a button to connect Jira. Click "Connect Jira"
  4. Follow authorization flow - Same as Method 1, steps 3-4

Verifying Connection

Method 1: Test Query

In Slack, try:

@continuum show my tasks

If Jira is connected, you should see your Jira issues.

Method 2: Check Status

Run in Slack:

/connections

You should see Jira listed as "✅ Connected".

Permissions Explained

What Continuum requests from Jira:

  • Read issues - To show your tasks and issue details
  • Create issues - To create new issues when you ask
  • Update issues - To change status, assignee, descriptions
  • Add comments - To comment on issues
  • View projects - To list projects and their details
  • Transition issues - To move issues between statuses

All standard Jira permissions - nothing excessive.

Security

How credentials are stored:

  • • Tokens encrypted with Fernet (AES-128) before database storage
  • • Encryption key stored in secure environment variable
  • • Each workspace has isolated credentials (no cross-workspace access)