Otter Hours
Harvest time sync for Jira Cloud. Log time once, on the issue you are working on, and it lands in Harvest for billing and in Jira as a real worklog.
What it does
- One entry, two systems. Every entry made through Otter Hours is saved as a Harvest time entry and a native Jira worklog, linked to each other. Jira's time tracking fields and reports count it.
- Two-way sync. Worklogs added in Jira's own Log work dialog reach Harvest. Edits and deletes on either side follow on the next sync. Harvest entries whose notes name an issue key are linked to that issue.
- Timer and past dates. Start and stop a Harvest timer from the issue, or log a fixed amount for any date.
- Admin defaults. A Jira admin maps each Jira project to a Harvest project and each issue type to a Harvest task, so people rarely pick anything.
- Rovo agent. Ask "log 2h to OTT-12 for yesterday, code review" and confirm the preview.
- Built on Atlassian Forge. No servers of our own. Each person signs in to Harvest with Harvest's standard OAuth sign-in; there is no shared API key.
Documentation
- Setup
Install, connect Harvest, first entry.
- Admin mapping
Projects, tasks and sync health.
- Daily use
Timer, log time, sync and fixes.
- Rovo agent
Log and summarise time from chat.
- FAQ
Pricing, data, limits.
- Troubleshooting
When something does not sync.
Trust
- Security: how the app is built and how to report a vulnerability.
- Privacy policy: what is read, stored and sent, and for how long.
- A data processing addendum is available on request at support@stubbornotter.com.
Pricing
Free for sites with up to 10 users. Paid tiers are billed by Atlassian through the Marketplace, for example $125 a year for 25 users, $500 for 100 users and $1,250 for 500 users. See the Marketplace listing for every tier.