Linking time to Jira issues

Once you have connected your Jira account, you can attach any time entry to a Jira issue right from the entry form. Linking keeps your Time Trakkr hours and your Jira issues in step, and on opted-in projects it pushes those hours back to Jira as worklogs. Connecting Jira is covered in the Jira integration article; this page is about using the link once it is set up.

Linking an issue from the entry form

The Jira field only appears when your own Jira connection is active.

1. Open the time entry modal from your timesheet.
2. Find the Jira issue (optional) field.
3. Type into the box reading Search issues by key or text…. After two characters, matching issues appear in a dropdown, searched with your own Jira permissions.
4. Select an issue. Its key shows as a badge on the field.

To change your mind, select Unlink next to the badge and search again.

What linking fills in for you

Picking an issue does two helpful things when the entry is still blank:

• If the notes are empty, they are set to the issue key and summary, for example "ACME-42 Fix the export".
• If you have not chosen a project yet, Time Trakkr infers one for you (and a task, where it can) so you rarely have to pick it by hand.

The inference follows a clear order. First it checks the organization's Jira project map, which an admin maintains and which always wins. If the issue's project is not mapped, it falls back to where entries on that same issue prefix have landed before, preferring your own history. If it cannot tell, it leaves the picker alone for you to choose.

The organization project mapping (admins)

Admins can pin each Jira project to a workspace project so linked issues always resolve to the right one. This lives on the Integrations page, in the Jira project mapping card under Organization integrations.

1. Connect the org-level Jira mapping if it is not already (see the Jira integration article).
2. For each Jira project row, choose a workspace project. Leave it on Not mapped (infer automatically) to let history-based inference handle it.
3. Select Save mapping.

A pinned mapping is authoritative: any issue in that Jira project always infers to the project you chose, no guessing.

Pushing worklogs back to Jira (per project)

Mirroring hours to Jira is off by default and turned on one project at a time by a manager or admin. On a project's edit page, tick Push linked entries to Jira as worklogs (for members with a connected Jira account).

With that on, saving a linked entry adds or updates a matching worklog on the Jira issue, and deleting the entry removes the worklog. Each worklog posts through the member's own Jira connection and is attributed to that member, so people only ever write worklogs they could write in Jira directly. If someone has no Jira connection, their entries simply skip the push; nothing blocks the timesheet.

The coverage line on your timesheet

When your Jira is connected, your week's timesheet shows a small coverage note, for example "Jira: 3 of 8 entries linked this week." If some entries are still unlinked, it nudges you to link issues from the entry form. It is only a prompt; linking is always optional.