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 organization project mapping (admins)

An owner or admin can connect Jira once for the whole workspace to pin each Jira project to a workspace project. This is separate from your personal connection.

1. Under Organization integrations, find the Jira project mapping card.
2. Select Connect Jira and approve access. As with the personal card, a site picker appears if the account can reach several sites.
3. Map each Jira project to a workspace project and select Save mapping.

This org connection is only ever used to read the list of Jira projects so you can map them. It never posts worklogs. See linking time to Jira issues for how a saved mapping steers issue links to the right project.

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 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.