Nativelog — Support
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.netpart). - 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 do not see the Nativelog panel on a work item.
In Jira Software an app's panel is not open by default. On the work item, click the small apps button just under the title and choose Nativelog; it then stays on that item for everyone. In Jira Service Management, Nativelog is a button on the item's toolbar. Your week is always under Apps in the sidebar.
What does a number without a unit mean?
Whatever it means in your Jira. Each site has a default unit for time tracking, and out of
the box it is minutes: typing 15 logs fifteen minutes, exactly
as it would in Jira's own log work dialog. 1d and 1w are your
site's working day and working week. The hint under the field says which unit your site
uses, and the confirmation shows what was logged. If Nativelog cannot read your site's
setting it asks you to type the unit instead of guessing.
My timer showed 1:40 and two minutes were logged.
Jira stores worklogs in whole minutes, so Nativelog rounds a timer to the nearest minute before saving it: 1:40 becomes two minutes, 1:20 becomes one. A timer stopped before one minute is not logged, and the panel says so.
I logged time and the work item shows no time tracking bar.
The time is saved. The bar is a Jira field called Time tracking, and it only appears when that field is part of the item's layout. When it is hidden, Jira also hides the item's Work log tab, so your entry shows up under the All tab of the activity section instead. In a company-managed project Nativelog notices this and says so in the panel; in a team-managed project Jira gives no signal, so add the field to the work type if you want the bar and the tab. In a company-managed project, check the project's field configuration and screens.
Our site uses another app as its time tracking provider. What does Nativelog do?
It keeps writing native Jira worklogs, and Jira keeps accepting them. What changes is the item view: with another provider selected, Jira replaces the Work log tab with that app's panel, so entries made with Nativelog appear under the All tab and in that app only if it reads native worklogs. Nativelog cannot tell which provider a site uses — Jira only shows that setting to administrators — so it cannot warn you. If your site has chosen another provider, that app is probably where your team expects time to be logged.
The same entry is on one day in Nativelog and on another in a Jira report.
It should not be. Nativelog places every entry on the day it falls on in the time zone of your Jira profile, which is the zone Jira itself uses for you, and starts the week on the day your profile's language starts it. If the two ever disagree, please tell us your profile's time zone and your computer's, and the entry's start time.
Nativelog says "Times in" a zone that is not my time zone.
The week view and the date field tell you which time zone Nativelog received from Jira for you. Jira takes that zone from your Atlassian account (id.atlassian.com, Account preferences), and after a change it can take a few minutes to reach the API the app reads. If the zone shown stays wrong, change the time zone in your Atlassian account to any other zone, wait a minute, and change it back: that forces Jira to resync. Then reload the page. If it is still wrong after that, tell us which zone the app shows and which one your account has.
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. The one thing to do first is to have everyone stop any timer that is still running: a running timer has not been logged yet, and uninstalling deletes the app's storage for the whole site — every running timer, for every user, with no warning to them. Reinstalling does not bring them back.
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.