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.

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.