Jira Cloud Integration

Connect Jira Cloud when your team wants Keito time tracking to update native Jira worklogs. The workspace is connected by an admin, and each team member connects their Jira user so worklogs are attributed to the right person.

Requirements

  • A Keito Business plan subscription.
  • A Jira Cloud site.
  • Administrator access in Keito to connect the workspace.
  • Each user who syncs worklogs must connect their Jira identity.

What It Does

The Jira integration can:

  • Connect Keito to one Jira Cloud site.
  • Let individual Keito users connect their Jira accounts.
  • Detect linked Jira issue keys on timer entries.
  • Create or update Jira worklogs from Keito timer entries.
  • Optionally delete synced Jira worklogs when corresponding Keito entries are deleted.
  • Optionally update Jira remaining estimates depending on your setting.

How It Works

Jira Cloud uses a workspace connection plus user connections. A Keito admin connects the Jira Cloud site once. Each team member who needs worklog sync then connects their own Jira identity so Jira can attribute worklogs to the correct person.

When a Keito entry is linked to a Jira issue key and is eligible for sync, Keito creates or updates a Jira worklog for the connected Jira user. Keito stores the Jira worklog ID so later edits update the existing worklog instead of creating duplicates.

Connect Jira

  1. Go to Settings > Integrations > Jira.
  2. Click Connect Jira as a Keito admin.
  3. Authorise the Jira Cloud site.
  4. Return to Keito and review sync settings.
  5. Ask each team member who needs worklog sync to connect their Jira user from the same settings page.

Day-To-Day Workflow

  1. Start or record time in Keito against a project and task.
  2. Link the entry to a Jira issue key, such as WEB-184.
  3. Stop the timer or save the entry.
  4. Keito creates or updates the Jira worklog for the connected Jira user.
  5. The sync status is stored so retries and updates can target the same Jira worklog.

The integration is built around Keito timer entries. Manual entries can sync when they have the required Jira issue link and user mapping, but the core workflow is timer-to-worklog.

Sync Settings

SettingWhat it controls
Sync time entriesCreates and updates Jira worklogs from linked Keito entries.
Delete worklogsAttempts to remove the Jira worklog if the synced Keito entry is deleted.
Estimate handlingLets you choose whether Keito updates Jira remaining estimates or leaves them unchanged.

Data And Permissions

The workspace connection allows Keito to communicate with the authorised Jira Cloud site. User connections are required so worklogs are attributed to the Jira user who performed the work.

Keito stores the Jira worklog ID after sync. This lets later updates modify the existing worklog rather than creating duplicate worklogs.

Disconnect Jira

  1. Go to Settings > Integrations > Jira.
  2. Disconnect your Jira user if you only want to stop syncing worklogs for your own account.
  3. As an admin, click Disconnect Jira to remove the workspace-level Jira site connection.
  4. Confirm the disconnect.

Disconnecting a user connection stops Keito from creating worklogs as that Jira user. Disconnecting the workspace connection stops all Jira worklog sync for the workspace. Existing Jira worklogs remain in Jira unless they are deleted manually or by an enabled delete-sync action before disconnecting.

Troubleshooting

Worklogs are waiting for user mapping

Ask the team member to connect their Jira account. Keito cannot create a Jira worklog for a user who has not authorised Jira.

The wrong issue was used

Check the issue key linked to the Keito time entry before saving or stopping the timer.

A delete did not remove the Jira worklog

Delete sync is best effort. If Jira rejects the delete because of permissions or issue state, remove the worklog manually in Jira and check the user’s Jira permissions before trying again.