Frequently asked questions

It adds a time tracking panel to every Jira issue and a sync page to the Jira Apps menu. From the panel you start Harvest timers and log time; the entry is created in Harvest and a worklog is written to the Jira issue. On the sync page you transfer entries that were booked directly in Harvest and apply later changes and deletions.

A Jira Cloud site with the app installed, and a Harvest account with at least one active project assignment that has tasks.

Yes. Each Jira user connects their own Harvest login, and the app only ever processes that person's own time entries.

No. You connect through Harvest's OAuth sign-in. The app never asks for a password or a token.

No. There is no central configuration. Every user who can access the Jira site can open the panel and connect their Harvest account.

The panel is called "Harvest Two-Way Sync" and sits in the details area of every issue. The sync page is under Apps → Harvest Two-Way Sync.

English and German. The interface follows your Jira language until you choose one in the settings.

No. The app is built on Atlassian Forge and runs on Jira Cloud only.

The first Harvest account that your login returns. Forecast accounts are ignored. If you need a different account, contact support.

Open the issue, choose a Harvest project and task in the panel and select "Start Timer". The timer runs in Harvest, so you also see it in the Harvest apps.

No. Harvest runs one timer per person. If a timer is already running, the panel tells you whether it belongs to this issue or another one and lets you stop it.

Yes, up to three months back. Future dates are not accepted.

Either as hours and minutes, such as 0:15 or 1:30, or as a decimal, such as 1.5. A decimal comma works too.

The first line is the issue key followed by the issue summary. If you typed a note, it follows below. In the settings you can reduce the first line to the issue key alone.

If there is already an entry for the same day, project, task and issue with the same note, the app adds the time to it. That keeps your Harvest day readable.

Yes. Turn on "Show today's entries" in the settings; the panel then lists today's entries for the issue with an edit option. The change is saved in Harvest first and then appears in the Changes tab of the sync page, where you apply it to the Jira worklog.

Not from the panel. Delete the entry in Harvest; the Changes tab then offers to remove the matching Jira worklog.

Yes. Select them once and choose "Save as default".

Time moves in both directions. A booking made on a Jira issue is written to Harvest, and an entry that exists in Harvest becomes a worklog on its Jira issue. Changes and deletions in Harvest are carried over to that worklog. Worklogs created with Jira's own "Log work" dialog are not copied to Harvest.

Bookings you make in the Jira panel are written to Harvest and Jira immediately. Entries you book, change or delete directly in Harvest are transferred when you run the sync on the sync page. There is no background job.

It looks for a Jira link on the Harvest entry first, then for an issue key in the note, for example `KAN-12`. You can also assign an issue by hand on the sync page.

They are listed as Unassigned and are never synced. Search for the Jira issue right on the entry; when you synchronize, the app writes the issue key and link into the Harvest entry.

No. An entry is transferred once its timer has been stopped.

Three months, counted from the booking date. Older periods cannot be selected.

It is written under your own name, on the date of the Harvest entry, with the duration rounded to full minutes. The comment contains the issue key. The remaining estimate of the issue is left as it is.

No. The worklog comment contains only the issue key. Your note stays in Harvest.

The app is built to prevent that. Every worklog it creates carries a sync marker, and each entry is locked while it is being processed. If a request times out halfway, the next run finds the existing worklog and continues from there.

A previous attempt created the worklog but was interrupted before it could finish. The app found that worklog and reused it instead of creating a second one.

No. Everyone syncs their own entries with their own Harvest connection.

Yes. Worklogs created by another tool are not recognised. Their Harvest entries appear as New, and syncing them would create a second worklog. Start syncing from the day you switch.

New: ready to sync. Synced: Harvest and Jira match. Changed: edited in Harvest after the sync. Unassigned: no issue detected, or the issue cannot be opened. Running: the timer has not been stopped. Error: Jira could not be checked for this entry.

The entry is marked as Changed. The Changes tab shows what is in Jira and what is in Harvest now. Select the entry and apply it; the existing worklog is updated and no second one is created.

A different date, duration, note, project or task.

After you confirm it. The Changes tab lists the deletion, and applying it removes the matching Jira worklog.

It reports a conflict and skips the entry. The app does not overwrite a duration that was changed by hand. Set the worklog back to the value shown under "Previously in Jira" and apply the change again.

Updating and deleting worklogs affects reports and invoices. The app shows you each difference first and applies only what you select.

In Atlassian's Forge storage that belongs to your Jira site. Novari Software operates no servers of its own.

Your personal settings, your default project and task, the ID of the connected Harvest account, a sync record per transferred entry (Harvest entry ID, Jira issue key, worklog ID, booking date, duration, a checksum and timestamps), and a diagnostics log of the last 24 hours. Everything is stored per Jira account.

The time entries you create or edit: project, task, date, hours and the note, which includes the Jira issue key and, unless you switch it off, the issue summary. A link to the Jira issue is added to the entry.

No. The app has no backend of ours and sends us nothing. We only see a diagnostics file if you download it and send it to us yourself.

The OAuth tokens are managed by Atlassian Forge. They are never sent to your browser and are not stored by the app itself.

Read and write access to Jira work data (issues and worklogs), read access to Jira user data, the app's own storage, and Atlassian's personal data reporting. Outside Atlassian it connects only to Harvest's sign-in and API hosts.

Sync records for three months from the booking date, the diagnostics log for 24 hours. A cleanup runs every hour, also for people who never open the app again.

The app reports the stored account IDs to Atlassian once a week, as Atlassian requires. Everything stored for an account that has been closed is erased.

Settings → "Log out completely". The guide covers both parts: disconnecting in the app and revoking the Harvest authorisation in your Atlassian account under "Connected apps".

The app's actions and errors of the last 24 hours, with credentials and tokens redacted. It is created only when you select "Download logs", and it goes nowhere unless you send it.

Atlassian. The app is licensed through the Atlassian Marketplace and appears on your Atlassian invoice together with your other apps.

Time tracking and synchronisation pause and the app shows a notice. Your Harvest entries and Jira worklogs stay exactly as they are. A site administrator can renew the subscription on the Marketplace.

Your Harvest user is not assigned to an active project with tasks. Ask a Harvest administrator to assign you.

Harvest allows one running timer. Stop the current one in the panel or in Harvest, then start the new one.

Jira could not open that issue. The key may be mistyped, the issue may have been deleted or moved, or you may not have permission to see it.

Harvest limits how many requests an account may send in a short time. Wait a moment and try again.

Open your Atlassian profile under "Connected apps", revoke the Harvest entry there, then connect again from the panel.

The subscription for your Jira site has ended or has not been started. A site administrator can start or renew it on the Atlassian Marketplace.

Write to support@novarisoftware.com. Add the diagnostics file (Settings → Diagnostics → Download logs) and tell us roughly when the problem occurred.