Optional Mylyn and repository connectors

Timekeeper 2.0's native projects, tasks and activity editor work without Mylyn. Install Timekeeper Mylyn integration to track Mylyn activation and synchronize local tasks/categories. Install repository connectors separately. Keep the Eclipse 2026-09 dependency site enabled; the adapter requires Mylyn Tasks 4.12. See installation.

Recorded time is stored in Timekeeper's configured H2 database, not in Jira or another task repository. Removing a provider issue from Task List does not remove its recorded activities. Those records remain available for Workweek editing, labels and reports.

Jira compatibility candidate

Jira support for 2.0 is tracked in #230. The grouping and issue-key changes described here are merged into main through PR #236, together with automatic acceptance tests using the actual released connector.

The tested connector installation is JiraConnector 6.0.0.202605160149 with Eclipse 4.41, Java 21 and Mylyn 4.12. Its update site is:

https://gnl42.github.io/JiraConnector-update/

Install Timekeeper Mylyn integration, add the connector site through Help > Install New Software..., select Mylyn Tasks Connector: Jira, and restart. Add a Jira repository through Task Repositories and use the connector's own credential settings. Timekeeper does not manage Jira credentials or send its activities to Jira worklogs.

The candidate adds a Timekeeper section to Jira repository settings:

Group new issues by	Behavior
Jira project	Use the Jira project's display name. This is the default.
Mylyn category	Use the task's Mylyn category, or Uncategorized when none is present.
Custom field	Enter a REST field ID such as customfield_10001, or its full Mylyn ID attribute.jira.custom::customfield_10001. Option display labels are used when available.

A missing, empty or unavailable project/custom-field value produces None. Changing this setting affects new imports and preserves existing Timekeeper project assignments. Workweek displays issue keys such as TK-42; the numeric Jira issue ID is kept separately so a key change can retain the native UUID and recorded history. Offline key display can use the stored Jira browse URL.

Actual connector installation, restart and repository-settings UI have passed. The released connector's REST client, query/metadata mapping, task editor, activation, offline editing and second-process history preservation are tested automatically with synthetic REST responses. See the automated acceptance report. Live Jira Cloud and Data Center querying and authentication have not been verified. A known upstream Mylyn Task List theme-parser Error Log entry remains open. Installation and fixtures do not establish live Jira compatibility; #230 remains open for that acceptance.

Other Mylyn tasks

Local Mylyn tasks/categories require no repository connector. The adapter also groups GitHub tasks by their Mylyn category (or Uncategorized) and supports Bugzilla product grouping. This is an integration path, not installed-connector certification for those providers on the 2.0 baseline. Other connector types may supply external identities, but are not verified by the Jira tests.

The earlier Wiki instructions are archived separately. Their old storage claims and grouping-menu instructions do not apply to 2.0.