Nativelog — Support

Last updated: 27 August 2026

Email [email protected]. One person reads it, and that person built the app. Expect a reply within one business day; during the private beta, usually the same day.

What to include

Any of these that you have makes the answer faster and more likely to be right:

Your Jira site URL (the something.atlassian.net part).
The work item key, if it happened on one.
What you expected, and what appeared instead.
A screenshot of the panel or the week view.
Roughly when it happened, with your timezone — it helps to find the matching request.

Please do not send passwords or API tokens. Nativelog never needs them, and no genuine support request will ever ask you for one.

If something goes wrong with your time

Nativelog is built so that this is recoverable, and it is worth knowing why. Your hours are ordinary Jira worklogs. They are visible in the Work log tab of the work item and editable there, with or without this app. If Nativelog is broken, unavailable, or uninstalled, your logged time is still in Jira and still yours.

If a timer failed to save, the app keeps the timer running rather than throwing the time away, and the panel says so. Press Stop again once the problem clears — it checks for a duplicate before writing anything.

Questions that come up

Why does my time appear under my name and not the app's?

Because Nativelog writes worklogs as you, using Atlassian's asUser mechanism. It is the reason the app exists. It means worklogAuthor = currentUser() finds your hours, native reports count them, and nothing is orphaned if the app goes away.

Can I log time for someone else?

No. Nativelog only creates, edits and deletes your own entries, and that check runs on the server. If you hold Jira's "edit any worklog" permission you can still do it — from Jira's own Work log tab. This app is deliberately your timesheet rather than a tool for administering other people's hours.

Why can I only have one timer running?

One timer per person, across every work item. Starting a timer somewhere else logs the previous one first and tells you where it went. Multiple simultaneous timers are the most common source of orphaned, forgotten hours in time-tracking tools.

I just logged time and my week view does not show it.

Jira's search index takes a few seconds to catch up, and the week view has to search to know which items to read. Press Refresh. The worklog itself is already saved — you can confirm that immediately in the item's Work log tab, which does not go through the index.

A timer ran overnight by mistake.

Stopping a timer that has been running for more than twelve hours will not log it silently. The app shows the total and asks you to confirm, and offers to discard it instead.

Why is the Start button missing on some items?

Your Jira permissions on that project do not include logging work, so a timer there would have nowhere to go. The panel says so rather than letting you time work you cannot save. Ask a project administrator for the "Work on issues" permission.

What happens to my hours if I uninstall?

Nothing. They are native Jira worklogs and they stay exactly where they are. There is no export step and no lock-in, by design.

Reporting a security issue

Email [email protected] with "security" in the subject line. Please give us a reasonable window to fix the issue before disclosing it publicly, and we will keep you informed while we do.