Help / Integrations

Jira

Time Trakkr's Jira integration has two parts that work together: a personal connection that lets you link and search issues, and an optional organization-level connection that an admin uses to map Jira projects to workspace projects. Both live on the Integrations page. Using the link once it is set up is covered in linking time to Jira issues.

Your personal connection

Everyone who wants to attach entries to Jira issues connects their own account. This connection is personal on purpose: issues are searched with your Jira permissions, and any worklog Time Trakkr pushes is attributed to you.

  1. Open Integrations.
  2. Under Your integrations, find the Jira card. The badge reads Not connected.
  3. Select Connect Jira and approve access in Jira.

Once linked, the badge shows Connected. If your Jira account has access to more than one site, a picker appears next to the badge so you can choose which site to search; with a single site, its name is shown instead. Select Disconnect to unlink.

The workspace connection, and mapping rules (admins)

Admins see two more cards under Organization integrations, and they do different jobs.

Jira (workspace) is a second, read-only connection belonging to the workspace rather than to a person. Its only job is to read Jira's project and issue-type lists so rules can be built from them. It never posts a worklog. Select Connect workspace Jira and approve access; a site picker appears if the account can reach several sites. Its badge reads Reading as the workspace, not simply "Connected", because the personal card above it says that too and the useful question is connected as whom.

This is not the connection that logs your time. Every member, admins included, still needs their own personal Jira connection under Your integrations — that is the one that searches issues as you and posts worklogs attributed to you.

Jira mapping rules is where you say where a Jira issue's time belongs. It is always visible, whether or not the workspace connection exists: the rules are live either way, and a missing connection only means there is no list of Jira projects to pick from. You can still add a whole-project rule by typing its key. Issue-type rules need the connection, because an issue type is identified by a number only Jira can tell us. The rules themselves, including which one wins when several apply and how to check an issue before you rely on a rule, are covered in linking time to Jira issues.

Requiring a Jira issue on a task

A manager or admin can make a task take time only against a Jira issue: on the project's edit page, tick Needs Jira beside the task. It is set per task, so Engineering can need an issue on one client's project and not on another's.

The switch needs Jira connected — the workspace's connection, or at least one person's. Until then it cannot be ticked, and the page says to connect Jira under Integrations, because every entry on the task would be refused with nothing to check its issue against. If Jira is disconnected after a task was switched on, the task keeps the rule and the page warns that new time on it is refused; you can still switch it off.

With it on:

  • New time on that task needs an issue that exists in Jira. The timesheet, the timer, the assistant, Slack and the API all refuse an entry on it without one. The issue field says it is required for that task; you can pick a search result or type the key, such as ENG-123.
  • The issue is checked against Jira when you save, using your Jira connection, or the workspace's if you have none. If Jira says there is no such issue (or none you can see), the entry is refused. If Jira does not answer, the entry is refused with a message to try again, rather than saved unchecked. If there is no Jira connection at all, the entry is refused and says to connect Jira.
  • Timers ask for the issue when you start them, so a running timer can always be stopped and saved.
  • Existing entries are left alone. Fixing the hours, notes or date of an entry made before the rule is fine. Moving an entry onto that task, or changing or removing its issue, is checked.
  • Copying rows leaves that task out. "Copy rows from last week" and copying a day's rows at zero hours would add an entry with no issue, so the task is skipped and named. Add that entry yourself with its issue. Copying a day with time and notes copies each entry with its issue, checked as any new entry is.
  • Agent time cannot go on that task. Agent time is never logged to Jira and never carries an issue, so it is not accepted onto a task that needs one — automatically or by you. It waits in your pending list, which says why; accept it onto another task, or discard it. An accepted agent entry cannot be moved onto such a task either.
  • Imported history is not refused.

How permissions and attribution work

Keeping connections personal is what makes the integration safe:

  • Searches run as you. When you search issues from the entry form, Time Trakkr uses your Jira permissions, so you only ever see issues you could see in Jira.
  • Worklogs are attributed to you. When a project has worklog push enabled, each mirrored worklog posts through the member's own connection and shows up in Jira as their worklog — never someone else's.
  • The org connection reads, it does not write. The admin mapping connection lists projects and issue types only; it cannot create worklogs, so it does not act on anyone’s behalf.

Turning on worklog push

Linking issues works as soon as you connect. Mirroring hours back to Jira as worklogs is a separate, per-project choice made by a manager or admin on the project's edit page, so it never happens without a Jira account behind it. The full behavior, including how the entry's project and task can fill themselves in, is described in linking time to Jira issues.

Updated 2026-10-08. Still stuck? Contact support or return to the Help Center.