Troubleshooting

Most problems show a message in the Otter Hours panel or in the admin's sync health. Start there.

I cannot find the Otter Hours panel

"Reconnect Harvest" or "Your Harvest sign-in expired"

Harvest no longer accepts your sign-in, for example because the access was revoked in Harvest or the password changed. Choose Reconnect in the panel and sign in again. Changes made in the meantime are waiting and sync once you reconnect.

I picked the wrong Harvest account

Choose Disconnect in the panel, then Connect Harvest again. Otter Hours picks the site's Harvest account if you belong to it, or asks you to choose. Admins change the site's account under Harvest account on the settings page.

"No default Harvest project (or task) is set"

The issue's Jira project has no Harvest project, or its issue type has no task and there is no default task. A Jira admin can fix this under Projects and Tasks on the settings page.

"Harvest locked this entry"

The Harvest entry is approved or invoiced, so Otter Hours will not change it. Someone with permission in Harvest must unlock or adjust it, or you can set the Jira worklog back to match. Then choose Dismiss on the message.

"Both sides changed"

The same entry was edited in Jira and in Harvest before a sync. The newer change was kept, and the message says which values were replaced. If the older change was the right one, edit the entry again in either place.

A worklog I added in Jira is not in Harvest yet

A Harvest change is not in Jira yet

The Rovo agent says it cannot use my Harvest sign-in

Some Rovo conversations do not pass the Harvest sign-in to apps. Logged time still goes into Jira at once and reaches Harvest the next time you open the panel. Start and stop timers from the panel. See Rovo agent.

The panel says the licence is inactive

Otter Hours is read-only until the site's licence is renewed through Atlassian. Nothing is lost.

Still stuck?

Email support@stubbornotter.com with your Jira site address, the issue key, roughly when it happened and the message you saw. Do not send passwords or API tokens.