Admin mapping and sync health
The Otter Hours settings page lets a Jira administrator decide where time goes, so people only enter how long they worked.
Open it from Apps > Manage your apps > Configure next to Otter Hours. Only Jira administrators can open or change it; the app checks the Administer Jira permission on every request.
Licence
Shows the site's Marketplace licence. If the licence becomes inactive, Otter Hours turns read-only: people can see their entries, but nothing new is logged or synced. No data is deleted, and syncing resumes when the licence is renewed.
Harvest account
Connect your own Harvest sign-in to choose the Harvest account this Jira site logs time to, and to load its projects and tasks. If you belong to several Harvest accounts, pick one from the list. Your sign-in is used for the settings page only; each person logs time with their own sign-in.
Projects
Each Jira project has a row:
- On: whether Otter Hours acts in this project. In projects that are off, the panel says so and the app ignores worklogs.
- Harvest project: where time logged on this project's issues is billed.
Tasks
- Default task: the Harvest task used when an issue type has no task of its own.
- Issue type rows: a Harvest task for each issue type, for example Bug to Bug fixing and Story to Development.
Choose Save settings when you are done. Changes apply to new entries; existing entries keep their project and task.
How an entry finds its project and task
- The Harvest project comes from the issue's Jira project mapping.
- The Harvest task comes from the issue type's mapping, or the default task.
- If either is missing, the entry is not logged and the person sees: "No default Harvest project (or task) is set for this issue. Ask your Jira admin to map it."
Sync health
- Last sync on this site
- When anyone's time last synced.
- Mappings to fix
- Appears when a mapped Harvest project was archived or removed, or a mapped task is no longer available on its project. Remap it, then save.
- Connected people
- Everyone who has connected Harvest, when they last synced, how many Jira changes are waiting to sync for them, and whether their Harvest sign-in needs reconnecting. Use it to see who has not connected yet.
- Recent conflicts and failures
- Every change that could not sync in the last 30 days: when, who, which issue and what happened. People can dismiss these from their own issue panel once they have read them, but they stay listed here until they are 30 days old.