docs/integrations/jira

Jira Integration

v1.3.0last modified 2026-03-27

Generate API Token

PRO PLAN REQUIRED

1. Go to id.atlassian.com/manage-profile/security/api-tokens

2. Click "Create API token"

3. Label: "Ekachit Integration"

4. Copy the generated token immediately (shown only once)

⚠ Never share your API token. Ekachit encrypts it server-side immediately after you enter it. It is never stored on your device.

Connect Jira

Enter your Jira credentials in Ekachit:

// required fields

instance_url: yourteam.atlassian.net

email: your Atlassian account email

api_token: the token from step 1

Ekachit validates the connection by fetching your assigned issues. If validation fails, double-check the instance URL (no trailing slash) and confirm the token hasn't expired.

Project Sync

sync configuration

project_selection:choose which Jira projects to sync

issue_filter:only issues assigned to you

sync_interval:every 30 minutes

initial_sync:imports open issues on first connect

direction:Jira → Ekachit (import), optional Ekachit → Jira (status)

Task Import

Jira issues are mapped to Ekachit tasks automatically:

// what maps from Jira → Ekachit

Summary → Task title

Story Points → Time estimate (× multiplier)

Status → Task status (To Do, In Progress, Done)

Subtasks → Checklist items (up to 30)

Priority → Task priority (preserved)

Issue Key → Jira reference (e.g., PROJ-123)

Imported tasks show a Jira badge with the issue key. Clicking it opens the issue in Jira.

Estimation Mapping

Story points are converted to estimated hours using a configurable multiplier:

// estimation formula

estimated_hours = story_points × multiplier

defaults:

multiplier = 2.0 (1 SP = 2 hours)

examples:

1 SP → 2h

3 SP → 6h

8 SP → 16h (~2 days)

🧠 After you complete ~10 Jira tasks, the ML engine analyzes your actual completion times vs estimates. It then suggests a personalized multiplier adjustment. Some developers run at 1.5x, others at 3x — the ML finds your number.

Two-Way Status Sync

Optionally sync task status back to Jira when you complete tasks in Ekachit:

status sync behavior

ekachit_done:Jira issue transitions to 'Done' (configurable target)

ekachit_in_progress:Jira transitions to 'In Progress'

jira_status_change:reflected in Ekachit on next sync

conflict:Jira wins (server-side is source of truth)

Enable per-project: Settings → Integrations → Jira → [Project] → Two-Way Sync → ON.

# Status transitions depend on your Jira workflow. Ekachit uses the default transitions. Custom workflows with required fields may need manual transition.

What We Access

✓issues assigned to you (read) — for task import

✓issue status transitions (write) — for two-way sync

✓project names (read) — for project selector

✓story points and priority (read) — for estimation

What We Don't Access

✕comments on issues

✕attachments or linked documents

✕other users' issues or profiles

✕board configurations or sprints

✕admin settings or permissions

✕webhooks or automation rules

✕time tracking logs from Jira

Common Issues

Authentication failed

Regenerate your API token at id.atlassian.com. Tokens expire if your Atlassian password changes.

Issues not importing

Verify: 1) The project is selected in sync settings, 2) Issues are assigned to you, 3) Issues are not in a 'Done' status (closed issues skip by default).

Status sync failing

Check your Jira workflow. If the 'Done' transition requires fields (like resolution), the automatic transition will fail. Use a workflow with unrestricted transitions.

Story points missing

Ekachit reads the standard 'Story Points' field. Custom point fields (e.g., 'Effort') need manual mapping in Settings → Integrations → Jira → Field Mapping.

Disconnect

Settings → Integrations → Jira → "Disconnect"

immediate: API token deleted from server

immediate: No more sync requests to Jira

preserved: Imported tasks remain in Ekachit (source: jira badge)

We recommend also revoking the token in Atlassian: id.atlassian.com → Security → API Tokens → Revoke.