Daily use
Everything happens in the Otter Hours panel on the Jira issue you are working on.
Run a timer
- Under Timer, add optional notes and choose Start timer. The timer runs in Harvest, so it keeps running if you close the page.
- The panel shows the running timer and its issue. Choose Stop when you are done. The time is saved in Harvest and as a Jira worklog.
Only one timer runs at a time. Starting a timer stops any timer already running in Harvest, including one left running from an earlier day. A timer started from Otter Hours is logged to Harvest and Jira as it stops.
Log time for any date
- Under Log time, pick the date. Past dates are fine.
- Enter the time spent. Otter Hours reads
2h,1h 30m,1.5h,90mand1:30. A bare number under 10 is hours and 10 or more is minutes. - Add notes if you like, then choose Log time.
The Harvest entry's notes start with the issue key and title, for example [OTT-1] Build the pricing page, followed by your notes, and the entry links back to the Jira issue. Entries are rounded to the minute and must be between 1 minute and 24 hours. Dates follow your Jira time zone.
See and delete your entries
Your entries on this issue lists the entries you have logged on the issue through Otter Hours, with a total. To delete one, choose Delete, then confirm. It is removed from both Harvest and Jira.
Working in Jira or Harvest directly
- Jira's Log work dialog: a worklog you add on an issue in an active project gets a matching Harvest entry, using the admin's mappings. Edits and deletes in Jira follow.
- Harvest: edits to hours, date or notes of a linked entry update the Jira worklog, and deleting the entry removes the worklog.
- New Harvest entries: an entry you create in Harvest with an issue key in its notes, such as
OTT-1 review, is linked to that issue and gets a Jira worklog. This applies to entries created or changed after you connected.
When changes sync
| Change made in | Reaches the other side |
|---|---|
| The Otter Hours panel or the Rovo agent | At once: both sides are written together. |
| Jira (Log work dialog, worklog edits and deletes) | The next time you open the Otter Hours panel on any issue, or choose Sync now. |
| Harvest (edits, deletes, new entries with an issue key) | When you open the Otter Hours panel, the settings page or the Rovo agent, at most every 15 minutes. Sync now pulls them immediately. |
Syncing runs as you, with your own Harvest sign-in, so it happens when you use Otter Hours. The panel shows Last synced so you can see how current it is.
Sync rules
- No duplicates. Each Harvest entry is linked to exactly one Jira worklog, and the same change arriving twice is applied once.
- Both sides changed. If a linked entry was changed in both Jira and Harvest since the last sync, the most recent change wins and the other is listed as a conflict.
- Locked entries. Harvest locks entries that are approved or invoiced. Otter Hours never changes a locked entry; the Jira change is kept as is and flagged so you can fix it by hand.
- Only your own time. You can change and delete only your own entries, and the app acts only for people who connected Harvest.
"Some changes did not sync"
If a change on this issue could not sync, the panel shows what happened, for example a locked entry or a conflict. Fix it by hand if needed, then choose Dismiss to clear the message from your panel. Your Jira admin still sees it in sync health for 30 days.
Disconnect
Disconnect stops Otter Hours acting for you and clears your queued changes. Your existing entries stay in Harvest and Jira, and their links are kept so a later reconnect carries on. To remove Otter Hours' access in Harvest as well, revoke it under Authorized OAuth2 Applications in your Harvest profile.